Your enterprise, your rules
Configure access, visibility, sharing, budgets, and audit oversight in your enterprise tenant.
On this page
Availability: Enterprise controls are configurable in your tenant as part of the enterprise offering. The options shown depend on the capabilities enabled for your organisation.
Ahamo Enterprise gives your organisation control over how its AI builder is used: who can work together, which models they can use, where builds run, and how work is shared or published. Teams can build within the boundaries you set.
Organise work around ownership
Your enterprise tenant is the overall administrative boundary. Organisations group business units; workspaces organise teams; projects connect a brief to its deliverables. Apps, slides, and other deliverable types represent the outputs of that work.
Use the organisation and project guide to choose the right level. Grouping work and granting access are separate decisions: placing work in an organisation does not automatically make it visible to every member.
Decide who can see and share work
Configure visibility at the enterprise, organisation, workspace, project, and deliverable levels available in your tenant. Define who may discover, view, edit, manage, and share work; those are different permissions.
| Decision | What to establish |
|---|---|
| Internal visibility | Whether work is private to its team or visible to a wider authorised audience. |
| Collaboration | Who may invite collaborators and which roles they can grant. |
| External sharing | Whether outside collaborators or shared links are allowed, and who may create them. |
| Publishing | Who may release an app and which destinations and audiences are permitted. |
A link is not permission. Test visibility with an ordinary member and an external account, not only an administrator. Review the effective access at each level rather than assuming a parent setting grants access everywhere.
Access to the builder is also separate from access to a published app. App users need the appropriate sign-in and data-access rules even when the people building it share a workspace.
Control AI, placement, and spending
Enterprise and organisation administrators can configure models and composite models. They can also determine whether build sandboxes and published apps run in Ahamo Cloud or customer cloud.
Set budget ownership at organisation, workspace, and project level. Keep permitted spending separate from the credit balance that funds it. See Plans, credits, and usage for that distinction and the standard workspace views.
Keep work accountable
Auditability and traceability connect people, work, and releases. Use the audit log to review who acted, what was affected, and when; use app history to inspect how a deliverable changed.
For a complete enterprise review, include access and sharing decisions, model configuration, build activity, and publishing. Agree on the event coverage, retention, access to audit records, and any export requirements for your tenant. A full audit requirement should name the evidence needed, not assume every screen records every action.
Start with Audit and traceability.
Before inviting a team
Assign an administrator and a budget owner. Confirm the approved models, sharing rules, and cloud destinations. Then exercise one small project as a normal team member: create it, collaborate, review its history, and publish to an approved destination.
That gives your enterprise a practical operating model without making every builder an administrator.