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

# Administration overview

> Manage people, access, integrations, and single sign-on for your K16 workspace.

Open your account menu and select **Settings**. Use the **Organization** section to control who can enter your workspace and what they can do. Organization pages appear only when your role includes the required permission.

<CardGroup cols={2}>
  <Card title="Users" icon="users" href="/administration/users/manage-users">
    Invite members, assign roles, cancel invitations, and remove access.
  </Card>

  <Card title="Roles and permissions" icon="shield-check" href="/administration/roles/manage-roles">
    Create roles and give each role only the permissions it needs.
  </Card>

  <Card title="Integrations" icon="plug" href="/administration/integrations/overview">
    Connect source systems, validate configuration, and monitor sync health.
  </Card>

  <Card title="Data access" icon="key" href="/administration/data-access/roles">
    Control DataX entity access and sensitive-column visibility by role.
  </Card>

  <Card title="Single sign-on" icon="key" href="/administration/sso/overview">
    Configure and maintain SAML or OIDC identity providers.
  </Card>

  <Card title="Security policies" icon="shield-check" href="/administration/security-policies">
    Set password requirements and review workspace authentication requirements.
  </Card>

  <Card title="Snowflake connections" icon="database" href="/administration/snowflake-connections">
    Create, rotate, and remove role-scoped service connections from personal settings.
  </Card>
</CardGroup>

## Before you make a change

1. Confirm that you are in the intended workspace.
2. Identify the smallest role or access change that meets the need.
3. Keep another authorized administrator available for authentication changes.
4. Review the affected users, integrations, or roles after you save.

<Warning>
  Changes to roles, SSO, integrations, and data access can immediately affect other people. Test
  high-impact changes with a small group first.
</Warning>

## Why an admin page may be missing

The navigation reflects your effective permissions. For example, **Users** and **Roles** require user or role administration access. **Data access** requires role-management access and DataX availability. **Single sign-on** can be read-only when your role can view providers but cannot manage them.

See [Permissions](/administration/roles/permissions) for the permissions currently exposed in the role editor.