Tenant administration

Governance guide

Set up enterprise access, feature, sharing, and presentation controls without giving every builder administrative power.

On this page

Availability. Governance controls depend on the enterprise capabilities enabled for your tenant and on your own permissions.

Ahamo governance lets administrators set clear boundaries while builders keep a simple day-to-day experience. Start with the tenant-wide choices, delegate through roles, and then make exceptional access decisions on the exact workspace or app that needs them.

Follow the control path

  1. Accept tenant administration through the one-time link provided during setup.
  2. Review which features are available and which ones your tenant should use.
  3. Invite workspace members and define roles around responsibilities.
  4. Share an app only with the people who need it, then inspect any exceptional access decision.
  5. Configure the tenant's identity and presentation, including its theme.
  6. Use account activity to review meaningful recorded changes.

This order is guidance, not a required company workflow. Your organisation decides who owns each step and how approvals work.

Keep the boundaries distinct

  • Enabling a feature does not grant a member permission to use it.
  • Workspace membership does not grant access to every app.
  • App sharing does not automatically grant published-audience or customer-data access; the assigned role's permissions govern what the person can read or change.
  • Removing a direct role does not necessarily remove inherited access.
  • Blocking a person from one app does not remove their workspace membership.

Verify with ordinary accounts

Do not validate governance only while signed in as an administrator. For each sensitive change, test one account that should be allowed and one that should be denied. Confirm the exact workspace or app, the action each account can take, and what changes when access is removed.

Capabilities not documented as available

Customer-managed policy editing, hierarchical budget allocation, customer model governance, and customer-cloud placement are not described here as current self-service journeys. Domain and email-domain configuration are also outside this guide. A visible internal service or operator control is not evidence of a supported customer workflow.

On this page