Review a workspace account

What this achieves

The workspace record holds one customer’s account detail: who they are, what plan they are on, what their entitlements are, and who has a user account. It is an account screen, not a way into that company’s HR data.

Required role: Humavera platform staff.

Steps

Go to Platform → Tenants.
Select the workspace’s row to open its record.
Read the Overview tab for the account and subscription position.
Open the Users tab to see who holds a user account in that workspace.
Select All tenants to go back to the list.

The four tabs

Option	Description
Overview	Account detail, the current subscription, and where usage stands against the plan.
Subscription	The plan itself, plus per-workspace overrides on features, limits, and capabilities.
Credits	The AI credit position and the record of every credit movement.
Users	The user accounts that exist in that workspace.

What the Overview tab shows

Option	Description
Tenant info	Name, Slug, Domain, Industry, Size, Country, Status, and, on a trial, Trial ends.
Subscription	Plan, Status, Monthly price, and Billing cycle.
Limits	Employees, AI credits, and the count of modules enabled.

Employees here is a number. It is how many employee records the workspace holds, used to size the subscription against the plan, and nothing on this screen opens one of those records.

Example: HC Corp’s record shows the plan, the billing cycle dates, the credits used against the credits included, and a live employee count. It shows no employee’s name, pay, or leave.

What the Users tab shows

The Users tab lists the accounts that can sign in to that workspace: Name, Email, Status, and Roles. These are account facts — who has access and at what level — which is what you need to answer an access question or to fix a sign-in problem.

Example: if HC Corp reports that nobody can approve anything, this tab shows whether the person who should be an administrator holds that role and whether their account is blocked.

The boundary, stated plainly

A customer reading this page is entitled to know exactly where the line falls, so here it is.

Option	Description
Visible to platform staff	The workspace’s own account detail; its plan, entitlements, limits, and billing cycle; its AI credit balance and credit movements; counts such as how many employee records exist; and the list of user accounts with their status and roles.
Not visible to platform staff	The HR data inside the workspace — employee records, pay and payslips, leave, performance, documents, and everything else the customer’s own people work with.

The workspace record has no tab that reaches HR data, because there is no such view to open. The platform boundary is enforced by refusal rather than by convention: a request from this console for data belonging inside a customer’s workspace is denied.

That extends to the customer’s own audit trail. A workspace’s activity log belongs to that workspace, so it is not readable from this console and there is no platform-side equivalent of it.

What happens next

From here you change what the account is entitled to rather than what it contains — the plan on the Subscription tab, the balance on the Credits tab. Both change the live workspace, so read the plan page before you change one.