Agiled Docs

Create an organization when you need a separate workspace for another business, brand, client operation, or test environment.

Before You Create One

Create a separate organization when the data, billing, users, permissions, or public links should be separate. Do not create a new organization just to add a new project, client account, team, product, or department inside the same business.

If you are unsure, keep the work in the current organization and use projects, accounts, teams, or departments. Separate organizations are best when separation is a business, billing, security, or branding requirement.

Ask whether users need separate reports, separate billing, separate domains, or separate integrations. If the answer is no, a new organization is probably too much separation.

Create the Organization

Open Organizations.
Select Create organization.
Enter the organization name.
Review or edit the slug.
Select Create.

Agiled creates the organization and prepares access control for the new workspace.

The slug is generated from the organization name by lowercasing it and replacing spaces with hyphens. You can edit it before creating the organization.

Review the slug before saving because it may appear in workspace URLs and internal references.

Slug Guidance

Choose a slug that is short, stable, and recognizable. Good examples:

acme
acme-consulting
northwind-ops

Avoid temporary names, test labels for a production workspace, or slugs that look too similar to another organization you manage.

After Creation

Set up the organization before adding production data:

Business profile and regional settings.
Enabled modules.
Team members and roles.
Finance settings.
Integrations.
Data imports.

Also review domains and public page branding before sending customers any checkout, invoice, estimate, form, booking, or document links.

Create one test record in each module you plan to use before importing production data. This confirms settings, roles, and navigation are ready.

Do not connect live payment gateways, mailboxes, or custom domains until the organization name, slug, roles, and modules have been reviewed.

Avoid Accidental Fragmentation

Before inviting users or importing data, confirm this should be a separate organization. If the same business only needs another department, project, pipeline, or client account, keep it in the existing workspace so reports, billing, roles, and customer history stay connected.

Switch Into The New Organization

After creation, the organization appears in the organization list. Select Switch to this to make it the active workspace. Agiled clears the previous workspace cache and routes you into the selected workspace.

If the organization has a different workspace host or custom domain, the switch can redirect the browser to that host.

Empty Organization Checklist

Before inviting the wider team:

Complete business profile and regional settings.
Configure modules.
Configure roles and permissions.
Configure finance settings if invoices or estimates will be used.
Connect mailboxes, calendars, and payment gateways as needed.
Import core CRM, product, project, or HRM data.

After setup, switch out and back into the organization to confirm the workspace appears correctly in the organization list and routes to the intended URL.

Separation Checklist

Create a separate organization when it needs its own:

billing and plan
users and roles
customer data
public domain or brand identity
integrations and credentials
reports and finance records

Create an Organization