> ## Documentation Index
> Fetch the complete documentation index at: https://staging.docs.flowsign.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Setting up your organisation

> The order to set up sign-in, roles, members, branding and security when you bring a team onto Flowsign.

This guide is for the admin setting Flowsign up for a whole organisation. Each step builds on the one before it, so working through them in order saves you from inviting people twice or re-assigning roles later. Every step links to the full guide for that settings page.

Steps marked **Enterprise** or **Business** need that plan. On a lower plan, skip them; the rest of the order still holds.

<Steps>
  <Step title="Check your company details and plan">
    In [Company](/guides/settings/company), set the organisation **Name**. It appears across Flowsign and on every email your recipients receive.

    In [Billing](/guides/settings/billing), confirm your plan and set the **Billing email** for receipts and invoices. Check the plan before going further: single sign-on, user provisioning, extra workspaces, API keys and custom fields need **Enterprise**, and branding needs **Business** or higher. Your plan's seat limit also caps how many members you can invite or provision.
  </Step>

  <Step title="Verify your email domains (Enterprise)">
    Under **Verified domains** in [Organisation security](/guides/settings/security#verified-domains), add each domain your people sign in with, such as `yourcompany.com`, and verify it. Single sign-on can't be turned on until at least one domain is verified.
  </Step>

  <Step title="Turn on single sign-on (Enterprise)">
    If your organisation uses an identity provider, turn on **Enable SAML SSO** under [Single Sign-On (SAML)](/guides/settings/security#single-sign-on-saml).

    Test a sign-in with a member account on a verified domain before you go further. Once it works, turn on **Require SSO** so members on your verified domains can only sign in through your identity provider.

    <Note>
      Organisation admins can still sign in with their password when **Require SSO** is on, so you can't lock yourself out if your identity provider is unavailable.
    </Note>
  </Step>

  <Step title="Create your workspaces">
    If you split work by office, region or team, create a workspace for each in [Workspaces](/guides/settings/workspaces). Each workspace has its own packages, templates, contacts and members. Extra workspaces need the **Enterprise** plan.

    Do this before inviting anyone: the invite dialog asks which workspace each person joins.
  </Step>

  <Step title="Set up roles and permissions">
    Review the system permission profiles in [Roles & Permissions](/guides/settings/roles-and-permissions). Where none fits, clone the closest one into a custom profile and adjust it.

    As with workspaces, do this before inviting anyone, because every invitation is sent with a permission profile.
  </Step>

  <Step title="Bring your people in">
    Choose one way to add members:

    * **User provisioning (Enterprise).** Generate a SCIM token under [User provisioning (SCIM)](/guides/settings/security#user-provisioning-scim) and paste it into your identity provider. It then adds, updates and deactivates members for you. People it adds join the default workspace with the **Sender** profile, so move them or change their profile afterwards where needed.
    * **Invitations.** In [Members](/guides/settings/members), use **Invite member** and choose each person's workspace and permission profile. Revoke an invitation from **Pending invitations** if it went to the wrong person.

    Either way, each member counts towards your seat limit. Make a trusted colleague an organisation admin too, so you are not the only one who can manage settings.
  </Step>

  <Step title="Create groups">
    With members in place, set up [Groups](/guides/settings/groups):

    * **User groups** organise your team.
    * **Signing groups** let any one member of the group complete a recipient's step, for example a shared legal or HR inbox.
  </Step>

  <Step title="Add your branding (Business)">
    In [Branding](/guides/settings/branding), upload your logo and pick a brand colour, then check the preview email. Do this before anyone sends, so every recipient sees your branding from the first package.
  </Step>

  <Step title="Set security and retention policies">
    Back in [Organisation security](/guides/settings/security), decide on:

    * **Session timeout**: how long members stay signed in when idle, and at most.
    * **IP allowlist**: the networks members and API keys may connect from. It applies to API keys and user provisioning too, so include the addresses of any servers that call the API and of your identity provider.
    * **Data retention**: how long completed documents are kept before they are permanently deleted.
  </Step>

  <Step title="Build your templates">
    Turn the documents your team sends often into templates, with roles, fields, reminders and expiry. See [Building a workflow](/guides/building-a-workflow). If you plan to use [custom fields](/guides/settings/custom-fields) (Enterprise), define them first so your templates can use them.
  </Step>

  <Step title="Connect your systems (optional)">
    To send from your own software or react to signing events, set up [API keys](/guides/settings/api-keys) (Enterprise), [Webhooks](/guides/settings/webhooks) and [Integrations](/guides/settings/integrations). The [developer quickstart](/developers) walks through a first send from code.
  </Step>

  <Step title="Ask members to finish their own accounts">
    Point each member to [My account](/guides/account/my-account) to set their signature and initials, and turn on two-factor authentication if they sign in with a password. They choose which events reach them in [Notifications](/guides/account/notifications).
  </Step>
</Steps>

## Related

* [Getting started](/getting-started)
* [Settings overview](/guides/settings)
* [Organisation security](/guides/settings/security)