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

# Manage organizations, sign-in and security policies

> Group workspaces and coordinate staff access without exposing every workspace to every member.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Group workspaces and coordinate staff access without exposing every workspace to every member. Where to find it: Enterprise → Organization, Roles, Identity and Security

## Before you start

* Organization owner or administrator authority.
* Your IT administrator for single sign-on, directory provisioning or network restrictions.

## Steps

<Steps>
  <Step>
    Create or select the organization and review its members and roles. Invite only the intended people.
  </Step>

  <Step>
    Request attachment of a workspace and have its owner approve it. Grant workspace and inbox access separately.
  </Step>

  <Step>
    For single sign-on, have your IT administrator configure and test the identity connection and explicit account links before enforcing it. Save the offered recovery method securely.
  </Step>

  <Step>
    Review role assignments, directory mappings and staff or machine IP restrictions. Preview restrictive changes from your current connection before confirming them.
  </Step>

  <Step>
    Use audit history and export controls to review access changes. Follow the advanced identity guide for provider configuration and recovery procedures.
  </Step>
</Steps>

## Example

A company groups two support workspaces while allowing each service team to see only its own inboxes.

## Things to know

* Single sign-on means staff use an approved company identity provider. Directory provisioning manages membership mappings; it does not silently create or link accounts by email.
* Network restrictions can lock staff out if their address is not allowed. Review the preview and recovery method.

## What happens next

<Check>
  Organization governance is applied with explicit workspace access and a tested sign-in path.
</Check>

## If something goes wrong

<Warning>
  * Member sees no workspace messages: grant explicit workspace membership and inbox access.
  * Sign-in enforcement cannot proceed: complete the required owner test and recovery setup.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Invite your team and control access" href="/stackshift-support/team-and-roles">
    Give each teammate the access they need to answer customers or manage the workspace.
  </Card>

  <Card title="Support organizations and permissions" href="/stackshift-support/organizations-and-permissions">
    Group workspaces, invite staff and grant only the access each person needs.
  </Card>

  <Card title="Export, retain or delete Support data" href="/stackshift-support/data-and-privacy">
    Handle data requests deliberately and understand what deletion affects.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.