> For the complete documentation index, see [llms.txt](https://40factory.gitbook.io/wilson/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://40factory.gitbook.io/wilson/3.11/wilson-academy/settings-1/user-management-1.md).
# Admin users
As for users, each admin or "app user" is identified with name, lastname and email.
The "Status" column represents the user's status and can take on two values: "Accepted" to indicate that the user has accepted the invitation and has logged in at least once, and "Pending Acceptance" if the invitation has been sent but not yet accepted. Is it possible to resend invitation to users that not already accepted.
You can also change the role from admin to user.
Each admin can be associated with groups and bots.
### Admin users
Admin users are privileged users: they can access Wilson Academy, manage the Knowledge Base, access settings and customization sections. In the Knowledge Base section, they have access to all features and documents. In the settings and customization sections, they can make any modifications, and in the User Management section, they can create profiles and other accounts, both Admin and regular Usersn and groups.
Administrators can also disable users directly from the user management panel in order to revoke the access temporarily without deleting accounts.
{% hint style="info" %}
Only if they have assigned the proper permissions, as explained in the next chapters
{% endhint %}
#### **Company Administrator**
A **Company Administrator** is an Admin-level user who automatically receives:
* All permissions enabled by default
* Immediate access to every administrative capability
* Full visibility and control across the entire company workspace
No additional setup or permission adjustments are required.\
As soon as a user is assigned the Company Administrator role, they can fully manage the system.
The Company Administrator role provides:
* **Consistent permission management** without manual configuration
* **Reduced risk** of misconfigured access
* **Clear governance**, ensuring there is always at least one fully privileged admin within the company
It's possible to create a Company Administrator by changing the role of an admin or an user
{% hint style="info" %}
Company admin role can be assigned **only** by another company admin or a superadmin
{% endhint %}
### Create user
Is possible to add an admin by clicking the "Add" button, entering the first name, last name, and reference email.
### Permission management
{% hint style="warning" %}
Bots are no longer assigned from the dialog of Edit User through the function of bots assignement to profile.
{% endhint %}
Once the user profile is created, a new functionality allows to grant specific permissions to the admin. You can define \ or specific permissions on chat, knowledge base, settings and usage analytics.
#### Global permission dialog
Using the **Global Permission** dialog you can assign and manage permissions at application level, which are not specific to a section of knowledge base or bot.
On the left side of the menu, you can view the application's main features, along with a brief description of the specific features impacted. The number indicates the number of enabled features.
On the right side you can manage each permission for the selected functionality..
Once a permit has been modified, the count will be updated and the box that has undergone a change will be highlighted.
{% hint style="info" %}
Remember to save when exiting the dialog, in order to have the changes applied
{% endhint %}
{% hint style="info" %}
Please note that the features "Text to speech" and "Speech to text" are displayed and editable only if enabled at company level. Otherwhise they will not be shown.
{% endhint %}
#### Knowledge base permission dialog
The **Knowledge Base permissions** feature, allows to assign permissions on a specific folder or subfolder.
\
The Knowledge Base structure is displayed on the left side of the dialog.
When you select a folder, on the right you can assign or remove viewing, creation, upload, editing, and deletion permissions for files and folders.
{% hint style="info" %}
When you apply permission on a folder, same permissions will be inherited by child paths.
{% endhint %}
{% hint style="warning" %}
**When permissions are assigned in this specific dialogue box, the user will lose permissions globally.**
{% endhint %}
#### Bots permission dialog
The **Bots permissions** feature, allows you to select which bots can be queried by the user (access permission), as well as apply other management permissions to enable configuration editing, filters, etc. for each bot.
{% hint style="warning" %}
**When permissions are assigned in this specific dialogue box, the user will lose permissions globally.**
{% endhint %}
#### **Assign admins to groups directly**
As for the users, administrators can be assigned directly to one or more groups, by selecting "Add/Edit groups". The flow is the same as the users:
* From the Admin Profile, administrators can assign membership by toggling the group/subgroup flag to ON;
* While assigning the admin to a group/subgroup, administrators can also choose to **remove the user’s personal permissions**, ensuring that only the permissions inherited from the selected group/subgroup remain active.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://40factory.gitbook.io/wilson/3.11/wilson-academy/settings-1/user-management-1.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.