Contents
On this page
Permissions - Plugixa FAQ
Where this appears: Plugixa FAQ, then Permissions, under Configuration in the sidebar. Since 1.1.0. Only people who can manage the plugin’s settings see it.
WordPress roles answer “may this person use the FAQ plugin at all”. Permissions answers the finer question: which records, and what they may do to them. A writer can edit only the FAQs they wrote, a translator can edit every FAQ but delete none, and a support lead can publish while everybody else saves drafts.
Nothing changes until you save a role
No permission role exists out of the box. Until you save the first one, WordPress capabilities decide access exactly as before, so installing or updating the plugin changes nobody’s access.
Saving the first role switches permissions on. From then on, people who are not in any active role lose access to the FAQ app. The screen warns you about this before you save. Put everybody who should keep access into a role first.
Administrators are never limited. Anyone who can manage the WordPress site has full access whatever the roles say, so you cannot lock yourself out.
Access levels
Each row has a level for View, Create, Edit and Delete, and a Whole row control to set all four at once.
| Level | Means |
|---|---|
| All | Every record of that kind |
| Own | Only the records the person created |
| None | No access |
The rows are FAQs, Categories, Views and Shortcodes, which can all use Own, and Feedback, which is All or None.
Extra abilities
Under the access table, grouped as Content, Tools and Administration:
- Publish FAQs and take them down
- Import and export FAQs (including PDF export)
- Use the AI generator
- Change settings
Publishing needs both the publish ability and Edit access to that FAQ. Saving a draft, or saving a FAQ that is already published and stays published, needs only Edit. So a writer without the publish ability can keep improving a live answer, but cannot put a new one live or take one down.
Who holds a role
Who holds this role takes two kinds of member:
- People: individual users, found by name or username.
- Everybody in these WordPress roles: for example every Editor.
A person in several permission roles gets the most generous level from each of them.
Buttons follow the role
The admin hides what a person cannot use. Someone with Edit but not Delete sees no delete buttons. Someone without import rights does not see import. An editor opened by typing its address shows a clear notice instead of failing when they try to save.
The same checks run on the server, so they also hold for the REST API.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| People lost access after saving a role | The first role switches permissions on | Add them to a role |
| A writer cannot publish | Publishing is an extra ability | Tick Publish FAQs and take them down |
| A writer cannot edit a colleague’s FAQ | FAQs is set to Own | Set Edit to All |
| The Permissions entry is missing | The app is off, or this is the free build | Activate it in Apps |
| An administrator is not limited | Administrators are never limited | Working as intended |
What to do next
User roles controls the WordPress side: which roles may open the plugin in the first place.
Quick Links
Share