Software & Administrative Access Approval Form

Ganjier Guild Ecosystem · Registries

Form H

Software & Administrative Access Approval Form

Final Internal · Ecosystem staff

Purpose. Documents requests for system access or permission changes and records the approval workflow.

Applicability. Required for all new access grants, permission changes, and access expansions.

# Form H — Software & Administrative Access Approval Form ## Purpose Form H is the formal request-and-approval record for any new system access grant, permission-level upgrade, or access expansion across ecosystem shared infrastructure. It ensures that all access decisions are documented, reviewed by the appropriate approver tier, and entered into the access registry (Form G). Administrator-level and Privileged-Confidential access require LLC officer authorization before the Ecosystem Systems Administrator provisions access. ## Owner & Maintenance **Owner:** Ecosystem Systems Administrator receives and processes all Form H submissions. **Update cadence:** Submitted at time of access request; approval steps completed within the timeframes specified in the Operational Manual. Completed forms are filed in the Systems Administration folder (Governance Drive) and cross-referenced in Form G. **Live record location:** Governance Drive — Systems Administration folder. ## Fields Tracked ### Request Details - Date requested - Requestor name - Requestor role and contribution title (per Section 28A, if applicable) - Department / operational area - Entity affiliation (C6, LLC, Co-op, contractor, Navigator, Operator) ### Systems Requested - Google Workspace - Shared Drives — General - Shared Drives — Privileged-Confidential (LLC officer authorization required) - Slack - Trello - Klaviyo - Zoom - QuickBooks - WordPress / Cloudways - GoDaddy / DNS Management - Instagram - YouTube - LinkedIn - Governance Documents folder - Financial Systems - Other (free text) ### Permission Level Requested View Only / Contributor / Editor / Moderator / Manager / Administrator / Super Administrator *Note: Privileged-Confidential folder access and Super Administrator access require LLC officer approval.* ### Justification & Duration - Business justification (narrative) - Duration: Ongoing or Temporary (through a specified date) ### Approval Workflow - **Step 1 — Supervisor / Department Lead:** Approver name, role, date, and signature - **Step 2 — LLC Officer** (required for Administrator, Super Administrator, financial systems, or Privileged-Confidential access): Approver name, role, date, and signature - **Step 3 — Ecosystem Systems Administrator — Access Granted:** Granting administrator name, date access provisioned, systems provisioned, permission level assigned, Form G entry date, and scheduled review date ## Workflow 1. **Requestor completes** Form H fields and submits to their supervisor or department lead. 2. **Step 1 approver** (supervisor / department lead) reviews and signs within the Operational Manual's defined review period. 3. **Step 2 approver** (LLC officer) reviews and signs if the request involves Administrator, Super Administrator, financial systems, or Privileged-Confidential access; otherwise Step 2 is not required. 4. **Ecosystem Systems Administrator** provisions access upon receipt of all required signatures, updates Form G within seven days, and files the completed Form H. 5. **Review date** is set by the Ecosystem Systems Administrator and triggers a future access review in Form G. ## Cross-References - **Form G** — Every approved Form H generates or modifies a Form G entry. - **Form K** — Super Administrator access approved via Form H is cross-referenced in Form K for recovery credential management. - **Form A** — Participant's requested systems and permission levels on Form A may initiate a Form H submission. - **Form J** — Offboarding triggers review of all Form H-approved access for the departing participant.