Approvals and Full access

Permissions decide whether you may see or change a record. Approval decides whether an authorized operation should happen now. Era inherits your role; it does not create administrator access.

Where to find it

Web and desktop: permission button below the Era composer, Ask for approval / Full access. Pending work appears in chat approval cards or the approval surface opened by Era. Roles are at Settings → Organization → Roles & permissions.

Two modes

Ask for approval lets you inspect changes, sends and removals first. Full access reduces questions for permitted routine work; money, external messages and deletion can still require approval. It does not auto-approve another person's request or actions marked as requiring confirmation. Local engine file/terminal permissions and Era business-action approvals are separate gates.

Use an approval card

If you explicitly say “I approve these three pending requests”, Era can process eligible approvals. It cannot decide for you on its own. Archive, message-send, document-issue and site-publish tools wait for approval inside the call. Do not repeat the same operation because it is waiting.

Organization and computer preferences

Let Era run actions that normally ask for confirmation at /settings/ai is a separate administrator preference. It does not replace chat mode, role access or individual action requirements. Desktop control has its own computer permission card; see computer use.

Limits and automation

Read, write, delete, manage, approve, handle and export are separate permissions. Own-record restrictions still apply even if you select another person's rows. Event agents and workflows also check the acting person's current permissions. See roles and security model.

Approvals and Full accessshots/era-approvals