Shared-tenant operations
Runseal runs a governed scope for each company in a shared tenant today, and is building toward a single deployment where central IT delegates approved enterprise actions to each company, while keeping control over permissions, policies, execution identities and evidence.
A subsidiary may be responsible for its own workspaces, applications or identities without being entitled to administer the wider tenant.
Traditional delegation often grants access to the platform itself. Runseal is designed to delegate predefined outcomes instead.
Central group governance
Action contracts · policy · approvals · execution identities
Company A
Approved actions
Assigned resources
Company B
Approved actions
Assigned resources
Company C
Approved actions
Assigned resources
Runseal governance boundary
The constrained execution identity performs the action. No local user receives a Microsoft administrative role.
Shared Microsoft tenant
In the delegation model Runseal is building, a cross-company request would be evaluated by:
Caller identity
Who is requesting the action?
Group company
Which legal entity or organisational scope does the caller represent?
Requested action
Is the caller permitted to request this governed action?
Target resource
Does the resource belong to the caller's permitted scope?
Risk level
Does the action require additional review or approval?
Approval policy
Which local or central authority must approve it?
Execution identity
Which constrained workload identity is permitted to perform the action?
= A governed decision to execute or refuse.
The action types the delegation model would cover. Actions marked Roadmap are not yet built; the others exist as Runseal actions today, with cross-company delegation of them on the roadmap.
In this model, central IT will be able to remove an entity's permission to request an action, change its approval policy or revoke its assigned scope, without granting or removing broad Microsoft administrative roles from each user.
The delegated capability would exist through Runseal's governed action model, not through permanent access to the underlying platform.
Cross-company delegation in a single deployment is on Runseal's roadmap. Today, Runseal delivers this as a separate governed scope per company in the shared tenant.
Governed delegation is not tenant isolation. The model is designed to enforce explicit organisational and resource boundaries where the underlying Microsoft services expose a reliable scope that can be validated, relying on administrative units, subscriptions, resource groups, ownership groups, explicit entity mappings, metadata or separate execution identities.
Where an action cannot be safely scoped, Runseal refuses it rather than simulate isolation through naming conventions alone.
