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

# Manage your organization

> Configure people, access, feature boundaries, custom data, documents, and integrations.

Organization administration establishes who can work in Canary, what they can see, which modules are active, and how shared records behave. Keep these settings deliberate because they shape every team's daily workflow.

## Administrative areas

<CardGroup cols={2}>
  <Card title="Users and teams" icon="users" href="/help/admin/users-and-teams">
    Invite people, set organization roles, group assignees, and manage removal safeguards.
  </Card>

  <Card title="Features and recovery" icon="blocks" href="/help/admin/features-and-recovery">
    Turn optional modules on or off and recover preserved records.
  </Card>

  <Card title="Custom fields" icon="list-plus" href="/help/admin/custom-fields">
    Add typed organization data to assets, locations, parts, and work orders.
  </Card>

  <Card title="API keys" icon="key-round" href="/help/admin/api-keys">
    Create scoped credentials for public API integrations.
  </Card>

  <Card title="Profile and language" icon="languages" href="/help/admin/language-and-profile">
    Update personal identity details and choose the web-app language.
  </Card>
</CardGroup>

## Organization settings

Administrators can set:

* Organization name and logo
* Default work-order visibility for non-admin users
* Currency label used for cost values
* PDF accent color and footer
* Work-order PDF sign-off layout

Changing the currency relabels existing amounts. Stored and historical numeric values remain unchanged.

## Recommended administration order

1. Confirm organization identity, visibility, currency, and document settings.
2. Invite users with the narrowest role that matches their work.
3. Create teams for assignment and request routing.
4. Enable optional features and their prerequisites.
5. Define custom fields before large imports or API integrations.
6. Create separate API keys for each integration with explicit scopes.
7. Review recovery surfaces before removing records or turning modules off.

## Lifecycle principles

Canary preserves operational facts such as completed work, readings, stock movements, receipts, approvals, and audit history. Archive master data where recovery exists. Permanent removal and dependency-blocked deletion are called out on the relevant guide.

## Related pages

* [Set up Canary](/help/getting-started/quickstart)
* [Core concepts](/help/getting-started/core-concepts)
* [Troubleshooting](/help/troubleshooting/overview)