Working with multiple organizations

Flowtly Editorial Team2 min

Your Flowtly account can belong to multiple organizations. This is useful for managing separate companies, client accounts, or distinct business units from a single login. Each organization maintains its own data, members, and settings, completely separate from others.

Switching between organizations

The organization you are currently working in is displayed in the account menu. To switch organizations, open the account menu, then select the desired organization from the list of organizations your account belongs to. Flowtly will reload, displaying only the projects, finances, and people associated with the selected organization. Data, settings, and access do not carry over between organizations.

Joining or creating another organization

You can join or create organizations:

  • Joining an existing organization: Accept an invitation to your account from an existing organization. Upon joining, you will be assigned a role within that organization.
  • Creating a new organization: Create a new organization from the organizations menu to set up a new, separate workspace.

Roles and access are set per organization

Your role and associated permissions are defined separately for each organization your account belongs to. For example, you might have an Owner role in one organization and a Member role in another. Your access and capabilities within Flowtly will change accordingly when you switch between organizations.

Example use cases

  • A consultant keeps a separate organization for each client and switches between them as the working day moves from one engagement to the next.
  • An owner runs two companies from a single login, switching organizations to invoice and report on each independently.
  • A new team member is invited into an existing organization and switches to it once their onboarding elsewhere is complete.

App routes

Connection map

Refers toPart of
Documented hereDocumented elsewhere
audit-log records person. setting defines attribute. org-document access governed by setting. subscription gates setting.recordsdefinesaccess governed bygatesAAudit trail — The record of who did what and when. It is how a user action is investigated after the fact, and what compliance is demonstrated from.Audit trailPPerson — An employee. The central record the rest of the workforce data hangs off — profile, documents, leave, benefits, rates.PersonSSetting — Platform-wide configuration — behaviours, permissions, security.SettingAAttribute — A custom data field defined once and collected across the platform, so an organisation can record what Flowtly does not ship a field for.AttributeDDocument — An organisational file, stored with control over who can reach it.DocumentSSubscription — The plan the organisation is on, and what it is billed for.Subscription