Organizations, Users and the Audit Log
How the Admin platform models organizations, the cross organization user registry, and the compliance audit log you use to trace activity.
The Admin platform organizes everything around three connected ideas: the organizations on the platform, the people who belong to them, and the record of what those people did. Understanding how these three surfaces relate makes the rest of Admin easier to navigate.
This article walks through each one at the concept level. It describes what the data represents and how the pieces fit together, rather than prescribing specific clicks.
Organizations
The Organizations area is the master directory of every organization on the platform. Each organization carries a set of core attributes:
- Name and subdomain. The organization's display name and the subdomain that identifies it.
- Logo. The brand mark associated with the organization.
- Subscription status. Where the organization stands in its subscription lifecycle.
- Enabled services. Which Humareso products the organization uses, drawn from Engage, Leave, Hub, Portal, Verify, Handbook, Fax, Agent, and Observe.
- Feature flags. Per organization switches that turn capabilities on or off for that org.
Each organization also has a detail view that surfaces engagement metrics, giving a sense of how actively the organization is using the platform. Removing an organization is handled as an archive, a soft delete that keeps the record rather than erasing it.
The user registry
The Users area is a cross organization registry, meaning it spans people across all organizations in one place. For each person you can see their email, name, role, status, and last login.
Roles describe what a person is allowed to do and include superadmin, admin, manager, and user. Status reflects whether the account is active, and last login helps you spot dormant or recently active accounts.
Each user has a detail view with an activity timeline and a list of the services granted to that person. Service grants connect an individual to the specific Humareso products they can reach, which is the user level counterpart to the enabled services you see at the organization level.
The compliance audit log
The Audit area is a compliance log of user actions across the entire platform. It is the system of record for who did what, and it is built for tracing activity after the fact.
The log is filterable so you can narrow a broad stream of events down to what matters:
- User. Focus on the actions of a specific person.
- Organization. Limit the view to a single organization.
- Service. Isolate events tied to a particular Humareso product.
- Action type. Filter by the kind of action that was taken.
- Date range. Choose a window such as the last 24 hours, 7 days, 30 days, 90 days, or a custom range.
Combining filters lets you answer precise questions, such as what one user did inside one service over the past week.
How do organizations and users relate?
Organizations define which services are enabled at the org level. The user registry then records service grants per person, so an individual's access is the user level reflection of what their organization offers.
Can an organization be deleted permanently?
The documented behavior is archive only, a soft delete. Archiving retains the organization's record rather than removing it outright.
How far back can the audit log reach?
You can filter the audit log by date range, including the last 24 hours, 7 days, 30 days, 90 days, or a custom window, alongside filters for user, organization, service, and action type.