Teams and access

Organisations, workspaces, and folders

Understand how your enterprise, organisations, workspaces, folders, and the apps, decks and documents Ahamo makes fit together.

On this page
  1. Enterprise tenantYour company’s administrative home.
  2. OrganisationA business unit and its configuration.
  3. WorkspaceShared apps, plan, and credits.
  4. ProjectOne brief and a shared outcome.
  5. Connected deliverables
    AppsSlidesOther outputs
A way to organise work, not an automatic access grant. Organisation grouping is optional; deliverable types depend on your tenant.

Your account identifies you. Your enterprise tenant provides the overall administrative boundary. Within it, organisations group business units, workspaces bring teams together, and folders keep related work side by side.

Availability. Organisation-level controls and the kinds of work you can make depend on your tenant's enterprise configuration. The hierarchy describes how work is organised; it is not an automatic grant of access.

Choose the right level

LevelWhat it is forWhat to check
AccountA person's sign-in and access to workspaces.Each person uses their own account.
Enterprise tenantThe overall administrative home for your company.Who governs models, sharing, cloud placement, and access.
OrganisationA business unit or other grouping inside the enterprise.Which workspaces and configuration belong to that unit.
WorkspaceA team working context with shared work, files, credits, and settings.Who collaborates and which workspace is active.
FolderApps, chats and files that belong together, with a brief the AI reads.Who the folder is shared with.
AssetSomething Ahamo made, such as an app, a deck, a document or a dashboard.Who can see, change, share, or publish it.

Keep related work together when the same team should collaborate and share credits. A workspace can also stand on its own without an organisation grouping; not every team needs every level.

One folder, several kinds of work

An app is an interactive product with its own code, data, history, and releases. A deck, a document or a dashboard is something people read. They can sit in one folder without becoming one app or sharing an app database.

For example, a customer-onboarding folder might hold an onboarding app, a deck for a stakeholder review, and the chats and files behind them. Its brief says what the folder is for, and Ahamo's AI reads it whenever it works on something in the folder. See Files and folders.

Separate apps when they need independent behaviour, data, or release lifecycles.

Make visibility deliberate

Enterprise administrators can configure visibility and sharing at the relevant levels. Membership in an organisation, or access to a folder, should not be treated as permission to see all underlying work. Moving something into a folder changes who sees it, and the dialog says so before you move it.

See Your enterprise, your rules for internal visibility, collaboration, external sharing, and publishing controls.

Separate funding from budgets

Enterprise spending requirements may apply across an organisation or within a workspace. A shared workspace credit balance is the funding source; it does not by itself express every spending limit your organisation needs.

Agree on budget ownership and allocation independently of where people sign in or work is grouped. See Plans, credits, and usage for the current controls and the scope to confirm for an enterprise rollout.

Separate platform access from app access

People who build in Ahamo and people who use a generated app are different audiences. Being a workspace member does not define who should see private records in an app.

Define those app access rules explicitly and test them with separate accounts. See security and data review.

Check context before acting

Confirm the workspace before starting a build or changing a plan. Confirm the app and environment before inspecting data or publishing.

Switching workspaces does not move apps or transfer credits.

Next, see Create and switch workspaces.

On this page