Status
The Status page answers two questions: what is in force right now, and is everything running? If you may not view Insights, it is your start page in companyADMIN.
At the top you see when the data was fetched (As of …) and the companyADMIN version. The page refreshes every five minutes; Check again queries immediately.
The page has five sections. Which ones you see depends on your rights:
- The first four sections need the right View configuration. Without it they do not appear at all; a notice takes their place.
- Roles at a glance also needs View roles, Admin sources also needs Access the admin area. If one of these is missing, the section stays empty.
- The Logs only appear with the right View audit log.
Extensions reachable
Section titled “Extensions reachable”This section shows whether the services of your environment answer: CompanyGPT itself and the extensions that are set up. The header summarizes the result, for example “11/12 reachable”.
| Column | Content |
|---|---|
| Service | Name of the service |
| Address | Address that is checked |
| State | Reachable, Not reachable or Switched off |
| Response time | Duration of the check in milliseconds |
| Version | Version of the service; per deployment if the service does not report it itself, otherwise unknown |
For most services Reachable only means that the service answers (Process answers). Whether everything behind it works is not checked. Only the AI Gateway and n8n report real readiness (Ready for work).
If something fails, the row gives the reason, such as No answer within 3 seconds or Connection failed.
Active configuration
Section titled “Active configuration”This section shows what really applies in CompanyGPT. The settings are made up of layers; a later layer takes precedence over an earlier one:
- Deployment default (YAML) – the base configuration maintained by innFactory
- Base for everyone – adjustments for all users
- Group
- Role
- User
Below that you find:
- Does not apply – stored adjustments that CompanyGPT does not apply
- Where the default wins – points where the default always takes precedence, such as the upper limit for subagents or MCP servers from the default
- Overwritten at start – rights that CompanyGPT resets at every restart. A change in companyADMIN lasts only until the next restart.
Open default and adjustments leads to the detailed view under Baseline & adjustments.
Roles at a glance
Section titled “Roles at a glance”The table shows each role with its Origin, the number of People and Hints. A click opens the role.
| Origin | Meaning |
|---|---|
| Role sync | The role is assigned automatically from Entra ID at sign-in |
| Admin role | The role whose name matches the admin group entry exactly (upper or lower case does not matter) |
| System | Shipped with CompanyGPT (ADMIN, USER). ADMIN itself usually appears here |
| By hand | Created in companyADMIN and assigned by hand |
Possible hints are No rights, Entra group unknown, Nobody holds it, Not in the role sync and Missing although registered.
- Create missing roles creates roles that are registered for automatic role assignment but missing. As long as such a role is missing, the people concerned cannot sign in. companyADMIN therefore also creates missing roles itself, at start and every five minutes afterwards, each with the rights of the USER role.
- Copy rights from “User” gives a role without rights the same rights as USER. You change individual rights in the role afterwards.
Role mismatches
Section titled “Role mismatches”If someone has a stored role that no longer matches their groups, they appear under Role mismatches. CompanyGPT only aligns the role at their next sign-in. Revoke sessions sets the role right away and ends running sessions where possible. Administrators are never changed.
The list is based on the group memberships CompanyGPT knows. People who have not signed in since the last reconciliation are missing from it; if CompanyGPT does not know the members of the role and admin groups, mismatches cannot be computed at all. In both cases the next sign-in still aligns the role.
Admin sources
Section titled “Admin sources”This section shows who is an administrator or an Insights user, and why. It is read-only.
| Column | Content |
|---|---|
| Source | The path through which access arises, such as Entra group, LibreChat role, LibreChat grant, OAuth role claim or a fixed user ID |
| Entry | The concrete value, for example the group or the role |
| Panel role | Administration (every section) or Insights (Insights only) |
| Hints | For example, which source your own session was admitted through |
Older paths are marked legacy. They still apply. Give new access to Insights with the right View Insights on a role or group.
For groups from fixed settings, Groups per setting shows the groups with their member count or the hint unknown in companyGPT.
Most sources are set by innFactory during setup. Contact innFactory if a further path should be added or one should be removed.
The Logs section contains the companyADMIN log and the companyGPT log. Both are described in Logs.