Organizations & Workspaces

Organizations

An Organization is the top-level container in OutDo. It represents a company, team, or entity and provides complete data isolation from other organizations.

What an organization contains

• Workspaces — One or more isolated application environments
• Members — Users added to the organization, sharing the organization's tier
• Variables — Custom key-value pairs accessible across all workspaces (e.g., API keys, shared configuration)
• Seat quotas — Seats backing the organization's paid tier: purchased via Stripe, or allocated manually by OutDo staff from the platform console

Organization properties

Property	Description
Name	Display name shown throughout the platform (e.g., "Acme Corp")
Internal name	Auto-generated from the display name, used internally (e.g., "acme_corp")
Owner	Full access everywhere in the organization. Assigned automatically to whoever created it, but transferable to another member afterwards — see Permissions
Variables	Custom key-value pairs referenced in integrations as {{org.variableName}}

Managing organizations

The Organization page lists every organization you belong to as a single-column list of full-width rows (not a grid). Each row shows the organization name, workspace count, and member count.

Editing an organization requires the Dev workspace role or higher (Dev, Admin, Owner) — either assigned org-wide, or held in at least one workspace of that organization. Qualifying users get a Configurar action in the row's overflow menu (⋮), which opens the organization's management dialog with these tabs:

Tab	What it does
Geral	Read-only summary: member, workspace, and active-subuser counts, plus creation date and creator
Configurações	Organization display name and color
Variáveis	Add, edit, or delete organization variables ({{org.variableName}}); a variable can be marked as a secret, which masks its value except for platform superadmins
Subusers	Manage the organization's subusers
Utilizadores	List, add, or remove organization members
Workspaces	List the organization's workspaces and pick the one that opens by default
Uso de AI	AI credit balance and usage breakdown by mode and model

This dialog is not the workspace Admin panel. Assigning roles or configuring visibility/operation overlays happens in the workspace's Admin panel → Permissions section instead, which requires the Admin role or higher — the Dev role does not reach it. See Administration and Permissions for the full model.

First-time setup

If you don't belong to any organization yet, the Organization page shows a welcome screen instead of the list. Click Criar a minha organização (Create my organization) to open the OutDo portal — organizations are created there, since billing and entitlements are managed in the portal. Once you're added to an organization, it appears back on this page.

Members and billing

The tier (plan) is assigned to the organization as a whole — every member shares the same tier. The organization Owner changes it from the portal's Subscription page (billing is never managed inside OutDo itself). Five tiers exist:

Tier	Price (per seat/month)	Workspaces	Records per workspace	Storage
Free	€0	1 (template-only)	2,000	5 GB
Basic	€12	1	25,000	20 GB
Pro	€32	5	100,000	50 GB
Scale	€55	Unlimited	250,000	100 GB
Enterprise	Custom	Unlimited	Unlimited	Custom

Seats are the capacity backing a paid tier — purchased through Stripe checkout, or allocated manually. Switching to a paid tier without enough seats for the current member count opens Stripe checkout for the shortfall; Enterprise without enough seats prompts a contact-sales message instead.

Seat usage (used vs. purchased), billing cycle dates, and manual-allocation history with its audit trail are visible to platform superadmins in OutDo's internal admin console — not to organization Admins inside the app.

Workspaces

A Workspace is an isolated application environment within an organization. Each workspace has its own features, views, modules, workflows, integrations, and permissions.

When to use multiple workspaces

• Separate departments — Sales workspace, HR workspace, Operations workspace
• Separate environments — Production workspace, Staging workspace
• Separate locations — Store A workspace, Store B workspace (using workspace variables for location-specific settings)
• Separate clients — Each client gets their own workspace within your organization

Workspace properties

Property	Description
Name	Display name (e.g., "Sales Operations")
Internal name	Auto-generated from display name
Default module	The module that opens first when entering the workspace (optional)
Module order	Custom ordering of modules in the navigation rail
Variables	Workspace-specific key-value pairs referenced as {{ws.variableName}}

Creating and editing workspaces

To create a workspace:

1. On the Workspace page, click Novo workspace (New workspace) — or A partir de template (From template) to start from one instead. Both are visible to the Dev workspace role or higher, either org-wide or in an existing workspace of the organization.
2. Enter a display name.
3. Click Save.

To edit a workspace, open its overflow menu (⋮) — same Dev+ gate as creating:

• Configurar opens the edit dialog: the Geral tab holds the name and default module, the Variáveis tab holds workspace-specific variables.
• Design opens the workspace's Admin panel — but that panel itself requires the Admin role or higher. A Dev-only user sees the Design entry in the menu but is redirected back to the workspace if they open it without Admin access.

First-time setup

When an organization has no workspaces yet, the Workspace page shows an onboarding screen instead of the list, and what it looks like depends on your role and your organization's plan:

• Free organizations don't see a template gallery at this stage. OutDo auto-creates a permanent Free workspace from the combined Essencial template (Tasks and Projects) while showing a brief "A preparar o teu workspace…" (Preparing your workspace…) screen. Continuar sem modelo (Continue without a template) is an escape hatch that drops you into the gallery if the auto-create is slow or fails.
• Non-free organizations see the template gallery instead: pick a ready-made template to create the workspace with its structure, views, and sample data already applied, or click Começar do zero (Start blank) to create an empty workspace instead. (A Free organization gets the same gallery later, for its trial workspace — see The trial workspace below.)
• Members without permission to create workspaces (below Dev) see a message asking them to reach out to someone with Dev access or higher to create the first one.

This onboarding only appears before the organization's first workspace exists. Once a workspace has been created, the regular list takes over, with the Novo workspace and A partir de template actions available to Dev-role-or-higher members as described above.

The trial workspace

Once a Free organization's permanent workspace exists, the Workspace page shows a banner: Experimentar o plano completo — 14 dias grátis (Try the full plan — 14 days free). It opens the same template gallery; picking a template creates a second workspace, flagged as a trial by the server. After 14 days the trial becomes read-only — no data is deleted — and the banner disappears once a trial exists. A trial is granted once per organization: recreating it doesn't restart the 14-day countdown.

Workspace cards carry a badge for these two cases: Free on the permanent free workspace, and Trial · N dias (or Trial · expirado once it lapses) on the trial workspace.

Free-plan limits: one Free organization per user, one Free workspace plus one trial per organization, 2,000 records per workspace, and one kiosk terminal. Where a limit is hit, OutDo shows a Fazer upgrade (Upgrade) prompt.

Workspace variables

Variables are key-value pairs that make your workspace configuration dynamic. They are referenced in integrations using the syntax {{ws.variableName}}.

Example use cases:

• storeId: "store-001" — Identify which store this workspace represents
• region: "EU" — Set regional configuration
• apiEndpoint: "https://api.example.com/v2" — Workspace-specific API endpoint

Combined with organization variables ({{org.variableName}}), this allows the same integration template to behave differently per workspace and organization.

Workspace navigation

When you click a workspace card:

1. OutDo checks for a default module. If set and valid, it navigates directly to that module.
2. If no default, it falls back to whatever module happens to be first in the loaded list — this is not guaranteed to match the Module order you configured in the admin panel.
3. Within the module, it checks for a default rail and navigates to it.
4. The view configured in that rail loads in the main content area.

Workspaces with no modules carry a Sem módulos (No modules) badge on their card and show a warning if you click them — they aren't visually dimmed.

Kiosk mode

Users flagged as kiosk accounts skip the organization and workspace selection entirely — kiosk is a flag on the user account, not a workspace role (see Permissions). Their account is pre-configured with a specific organization, workspace, module, and rail. On login, they are redirected automatically to their designated view — ideal for self-service terminals, point-of-sale stations, or dedicated workstations.