> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Organization, Entities, and API Access
> Organization administration controls the account container around your Arcus entities. Use it to review plan limits, create sandbox or production entities, manage entity status, and control personal API keys used by scripts and integrations.
**Organization tools affect the whole company**
Treat organization pages like security and operating controls. Creating a production
entity, deactivating an entity, or issuing an API key can affect users, integrations,
reporting, and data access across the business.
## Use the Right Admin Surface
Arcus separates organization-level controls from entity-level settings. This keeps
company access, billing limits, and entity creation separate from daily operating
settings like shipping, tax, users, products, and documents.
* **Organization Overview**: review the current plan, usage, and enabled features.
* **Entities**: create sandbox or production entities and deactivate or reactivate existing entities.
* **Organization Users**: invite people and assign them to one or more entities.
* **Roles and Entity Team**: tune what users can do inside an entity.
* **API Keys**: create personal entity-scoped tokens for scripts that act as your user.
* **Developers**: manage shared entity API keys, webhooks, logs, analytics, collections, docs links, and SDK links when your role allows it.
## Review the Organization Overview
Open **Admin**, then **Organization**. The overview shows the
current plan, subscription status, feature badges, and usage against limits such as
entities, users, and products.
If Arcus blocks a new entity, new user, or product expansion, check this page first.
A plan limit is different from a permission issue: a permission issue usually hides
or blocks an action for one user, while a plan limit affects the organization.
**Feature badges explain available workflows**
Feature badges such as API Access, AvaTax, PrintNode, marketplaces, or advanced analytics
indicate which optional capabilities are enabled for the organization. The detailed
connector setup still lives in Integrations or the matching settings page.
## Manage Entities
An entity is a separate operating company or environment inside the same organization.
Each entity has its own customers, products, inventory, accounting, documents, settings,
and user memberships.
* **Production**: live operating data. Use this for real orders, payments, labels, inventory, and accounting.
* **Sandbox**: test and training data. Use this before changing a production process.
* **Active**: users with membership can enter the entity.
* **Inactive**: the entity is no longer available for normal work, but its record remains in the organization.
**Do not use sandbox as a second production company**
Sandbox is for testing, training, and process rehearsal. Do not run real operations there
unless the team intentionally wants test-mode connectors, test-mode payments, and non-live
operating behavior.
## Create an Entity
Use **Create Entity** only when the business truly needs a separate company,
separate sandbox, or separate live environment. If you only need a warehouse, store,
ship-from address, or receiving location, create a location instead.
1. Open **Admin**, then **Organization**.
2. Choose **Entities**.
3. Select **Create Entity**.
4. Enter a clear entity name.
5. Enter a short uppercase entity code that operators will recognize.
6. Choose **Production** or **Sandbox**.
7. Create the entity.
8. Invite or assign the users who should access the new entity.
9. Complete the entity setup checklist before using it for live work.
**Set up the new entity before users start working**
After creating an entity, configure business profile, locations, document numbering,
tax, payment terms, shipping, integrations, users, roles, and opening balances before
operators use it for real workflows.
## Deactivate or Reactivate an Entity
Deactivation is an access and operating-control action. It is not a cleanup shortcut.
Use it when an entity should no longer be used for normal work, such as an old sandbox,
a retired division, or a duplicate entity created during setup.
* Confirm no team is actively using the entity.
* Review open orders, open POs, unpaid bills, unposted accounting work, and active integrations.
* Export or archive required reports before removing day-to-day access.
* Tell users which entity replaces it, if any.
* Reactivate only after confirming why the entity was disabled.
Entity tiles show active status, environment, member count, and location count. The
Deactivate or Reactivate action is separate from deletion.
## Delete an Entity or Close the Organization
Entity deletion and organization closure are primary-owner actions. Use them only
after deactivation, review, and internal approval.
* **Delete** appears only for inactive entities and only to the organization's primary owner.
* **Pending Deletion** means deletion has been scheduled and can be cancelled before the final removal window ends.
* **Last active entity** cannot be deactivated as a normal entity cleanup path. Arcus directs the primary owner toward the organization closure flow instead.
* **Close Organization** is the front-door action for closing the whole account. It previews affected entities, users, rows, and connector secrets, then requires typed confirmation and a final acknowledgement.
* **Pending Closure** means the organization is scheduled for teardown. The primary owner can cancel closure while the cancel action remains available.
**Deletion and closure affect data, users, and integrations**
Before scheduling deletion, export required records, stop integrations, notify operators,
and confirm which environment replaces the entity or organization. Do not use deletion
as a routine cleanup shortcut.
## Use Personal API Keys Safely
Personal API keys let scripts authenticate to Arcus as your user for the current entity.
They are useful for controlled reporting, scheduled imports, and operational automation,
but they should be handled like passwords.
Each key is entity-scoped. A key created while you are in one entity should not grant
access to a different entity. The key can also be scoped to specific permissions, and
Arcus will not allow you to grant a key more access than your own effective permissions.
Personal keys are different from shared Developers settings keys. Use personal keys for
scripts that should act as one user. Use Developers settings for owner/admin-managed
entity integrations, shared service keys, webhooks, logs, analytics, and collection downloads.
## Create an API Key
1. Open **API Keys** from the account or profile area.
2. Select **New key**.
3. Name the key after the script or job that will use it.
4. Choose an expiration in days. Shorter is safer.
5. Select only the scopes the script needs. Empty scopes mean unrestricted, so avoid leaving scopes empty unless there is a clear reason.
6. Create the key.
7. Copy the token immediately and store it in your secret manager.
**The full token is shown once**
Arcus displays the full API token only when it is created. If it is lost, create a new key
and revoke the old one. Never paste tokens into tickets, chat, screenshots, email, or docs.
## API Key Safety Rules
* Use one key per script or integration job so it can be revoked without breaking unrelated work.
* Prefer scoped keys over unrestricted keys.
* Use expirations and rotate keys on a schedule.
* Revoke a key immediately if it may have been shared, copied into logs, or committed to code.
* Remove keys during offboarding or when a script is retired.
* Review last-used timestamps to find stale keys.
## Common Blocks
* **Create Entity is blocked**: check your organization role and plan entity limit.
* **A user cannot see a new entity**: add the user to the entity from Organization Users and confirm their role.
* **An entity is missing from the selector**: confirm it is active and the user has an active membership.
* **Delete is missing on an entity tile**: confirm the entity is inactive and you are the organization's primary owner.
* **Close Organization is missing**: only the primary owner sees the organization closure danger-zone control.
* **API Keys page is unavailable**: your role may not include personal API key management or API Access may not be enabled.
* **Scope cannot be selected**: your user must already have that permission before a key can receive it.
* **Script stopped working**: check expiration, revoked status, entity context, and whether your role or scopes changed.
## Related Articles
Invite users, manage entity access, roles, permissions, location restrictions, PINs, and MFA reset workflows.
Review audit activity, saved filters, compliance reports, exports, integrity checks, and deep-linked audit entries.
Configure business profile, environment, branding, locations, and the workflow impact of company defaults.
Manage profile details, PIN lock, MFA, security keys, and recovery options.
Manage entity API keys, webhooks, usage logs, analytics, collection downloads, and docs links from the admin settings area.
Understand the admin surfaces, settings groups, and workflow impact areas.