What is a tenant, organisation or workspace?¶
A tenant, organisation or workspace is a provider-controlled environment used to group users, data, settings and permissions.
It is often the boundary around an employer, school, business, team or other customer.
What this means in practice¶
Within a tenant or workspace, administrators may create users, assign roles, control sharing, apply security policies and retain audit records. Files, messages, applications and settings may belong to the organisation rather than to the individual user.
A provider record showing an account name without the tenant context may be ambiguous. The same username may exist in several organisations. A guest user may also appear inside another organisation’s workspace while remaining controlled by an external identity provider.
What this may show¶
The tenant may have its own identifier, domain, region, administrators, retention settings and authentication arrangements. These details can be essential when directing a request or interpreting a log.
What this does not show on its own¶
The dangerous assumption is that the service is simply a collection of separate personal accounts.
The same cloud provider may host thousands of tenants. A user account in one tenant is not automatically connected to an account with the same email address in another.
What to do next¶
Identify the tenant or workspace whenever organisational cloud evidence is involved. Record the organisation name, domain, tenant ID, workspace ID, relevant administrators and the user’s role within it.
Ask whether the organisation retains audit logs, account-allocation records, device assignments and policy changes. The provider may hold technical records, while the customer organisation holds the human and business context.
Do not assume that an account leaving the organisation removes all related data. Files, audit records and ownership may remain within the tenant after the user is disabled or deleted.
Key takeaway
Treat the tenant or workspace as the organisational evidence boundary, and identify its administrators, identifiers, policies and records before interpreting user activity.