Skyboot AI Markdown Permissions: Control Who Can Use Each Feature

AI Markdown > Permissions lets administrators decide which WordPress roles and which individual people can use each part of Skyboot AI Markdown. For example, editors can fix content without touching settings, a freelance writer can see analytics, or one author can export. Only administrators see this tab.

Which permissions can I grant? #

Permission	What it allows
View AI Analytics	The AI Analytics tab: crawler visits, visitors from AI, pages AI reads
View AI Visibility	The AI Visibility tab: checklist, readiness scores, IndexNow status
Review & fix content	Review & Fix, applying fixes, re-scanning or excluding a page, and the AI Ready column buttons. Only on posts the person can already edit
Use the AI API key	Generate with your connected AI provider, which is billed to your API account. People without it can still use the ChatGPT, Claude, Gemini, Copilot and Perplexity buttons
Run site tools	Crawler access test, scan all content, submit all URLs to IndexNow, update crawler IP lists
Export content	Single, bulk and site-wide Markdown export
Import content	Markdown import (only for post types the person can create)
Manage plugin settings	Settings (including AI Visibility settings and Exclude my IP), Overview, Checker and System Status, regenerating llms.txt and purging the cache

What is always reserved for administrators? #

• Changing permissions
• The AI provider and API key
• Everything else as well: administrators always have every permission, so nobody can lock themselves out.

How do I set permissions by role? #

Tick the features each role gets. Only roles that can work in the WordPress admin are listed, because subscribers and customers cannot use these screens.

Defaults on a new install:

Role	Default access
Administrator	Everything
Editor	View AI Analytics, View AI Visibility, Review & fix content, Use the AI API key
Author	Review & fix content (their own posts)
Contributor and others	Nothing

How do I give one person different access? #

Add the person under For specific people, click Save permissions, then set each feature:

Choice	Meaning
Role (yes / no)	Follow the person’s role (shows what the role currently gives)
Allow	Give this person the feature, even if their role does not have it
Deny	Take the feature away from this person, even if their role has it

Click × next to a person and save to remove them. They then follow their role again.

What do people see? #

• The AI Markdown menu appears only for people with at least one permission, and only the tabs they may use are shown.
• Buttons for features someone cannot use are hidden. For example, without Run site tools the Scan and Run test buttons do not appear.
• Every action is also checked on the server, so hiding a button is never the only protection.
• Review & fix content never lets someone change a post they could not edit anyway.

What happens to permissions when I remove the plugin? #

Permissions are stored as one plugin setting. WordPress roles are never modified, so deactivating or deleting the plugin leaves your roles exactly as they were.

How can developers check a permission? #

Each permission is a capability, so you can check it in your own code, for example current_user_can( 'skyboot_view_analytics' ).

Capability	Permission
skyboot_view_analytics	View AI Analytics
skyboot_view_visibility	View AI Visibility
skyboot_fix_content	Review & fix content
skyboot_use_ai_api	Use the AI API key
skyboot_run_tools	Run site tools
skyboot_export	Export content
skyboot_import	Import content
skyboot_manage_settings	Manage plugin settings

FAQ #