Admin Access Register

Admin Access Register helps a business record who holds administrative rights on each system, who provides backup coverage, and when access was reviewed. The recommended structure uses one row per named admin account with a system, an owner, and a last-reviewed date. Shared logins receive early attention because unclear ownership makes offboarding harder.

The workflow begins by distinguishing a requested build, migration of an existing process, review, or advice question. It asks only for unanswered facts that affect the result, one at a time. Scope includes the systems, admin count, and whether accounts belong to employees or vendors. Ownership questions cover approval responsibility, named owners, and shared logins. Review context covers frequency, departure handling, retained evidence, and whether current records or tickets are up to date.

The proposed sequence lists a system, records its admin account, assigns owner and approver, schedules periodic review, and records removal. This is a documentation workflow rather than an account-management integration. A recommendation comes first for advisory requests; a confirmed artifact request proceeds to the requested formats after essential gaps are resolved.

Use it for an admin register, privileged-account inventory, or quarterly access review. A request about stale access after departure can be:

We have admin accounts for people who left two years ago.

The skill does not grant, change, or revoke permissions on a system and supplies no automation, reminders, or synchronization. It does not calculate payroll, taxes, leave balances, or KPIs. Real operational decisions still require the relevant human review.

Confirmed business context determines the register. Fields identify system or tool, category, main and backup admins, department, access level, admin-user count, billing owner, plan, seats, and renewal date. Account-control fields record company ownership, shared-login status, password-manager entry reference, and whether two-factor protection is on. Review fields include last and next dates and the offboarding checklist item. Risk, lifecycle status, notes, and an admin ID complete the record.

Access choices include Full, Write, Read, and No Access. Risk labels run from Low to Critical. Lifecycle status distinguishes Requested, Approved, Provisioned, Review Due, and Revoked. Numeric fields remain numbers, review and renewal dates remain dates, and control indicators remain booleans. The password-manager field is a reference rather than a place for secret values.

Requested CSV, SQL DDL, JSON Schema, Notion mapping, or workbook artifacts derive from one field list. Templates remain empty unless clearly synthetic examples are requested; generated rows do not contain real employee or customer information. Excel-compatible CSV uses UTF-8 with a byte order mark, while XLSX is created only when explicitly requested.

Notion output is routed to notion-manual-import for its mapping and verification. Manual artifacts need no connection. Live workspace changes require verified tool access and an authorized target. Imported identifiers stay text, and select, number, date, and checkbox properties are configured after import.