preset-admin

Use for Preset Management API administration beyond read-only workspace discovery.

Always

• Use preset-api first for auth/client setup.
• Default to read-only preflight and ID/role lookup.
• Resolve team, workspace, user, invite, and role identifiers from API responses before mutations.
• Get explicit confirmation before role changes, invites, member removals, workspace lifecycle actions, audit downloads, or any write.
• Use preset-roles-permissions for permission-sensitive role/access changes.

Decision Rules

• Classify membership role and invite changes as approval-gated mutations.
• Use metadata reads for membership, role, invite, and audit inspection.
• Require target and effect summary before any access change.
• Avoid applying invite or member role changes until approval is explicit.

Workflow Order

1. Identify team, workspace, user, invite, member, and role identifiers.
2. Inspect membership, role, invite, and audit metadata.
3. Prepare approval summary with target and expected effect.
4. Stop before invite, member role, removal, or workspace change.

Retrieve

• Team membership routing: references/team-memberships.md
• Team member lookup, seat checks, response fields: references/team-member-lookup.md
• Team role changes and removals: references/team-member-access-changes.md
• Workspace create/update/delete/un-hibernate: references/workspace-management.md
• Invites, cancellation, resend, bulk invite: references/invites.md
• Audit log lookup and downloads: references/audit-logs.md
• Role identifiers: references/role-identifiers.md
• Unsupported or adjacent Manager endpoints: references/deferrals.md
• Approval policy before writes/downloads: load preset-api and then references/safety-policy.md.

Do Not

• Do not use internal /api-internal/*, billing/payment, SCIM, API key CRUD, permission/DAR/RLS, or database connection mutation routes from this skill.