TemplateConnections & Permissions Plan
An inventory of every system a Clone will connect to, with scopes, credential owner, approval and review date, signed off by InfoSec before go-live.
#What this is for
Large AI rollouts rarely stall on the model. They stall on connections: who approved access to the ERP, which scopes the CRM token has, whose account the Clone is acting as. This plan answers those questions before anything is connected. It is the single list InfoSec reviews, and the record auditors ask for later. Because InfoSec is the first department we onboard, this plan is also how the likeliest blocker becomes a sponsor.
#When to use it
Build the first version in the InfoSec kickoff (Weeks 1–2). Add rows in the Design week of every department rollout, before the Clone Design Spec is approved. Review every row at least quarterly.
#Who's involved
- Implementation Engineer: proposes connections and scopes.
- InfoSec lead: approves, conditions or rejects each connection.
- IT lead and system admins: create service accounts, OAuth apps or API keys.
- Business owner: confirms the business need for each connection.
- GRC Clone: drafts rows and tracks review dates.
#How to fill it in
- List every system a Clone will read from or act in. Start from the Systems & Workflow Map.
- For each, choose the connection method and the account model (delegated user, dedicated service account, or per-user OAuth).
- Request the narrowest scopes that support the workflow. Write down why each scope is needed.
- Record the data classification of what the Clone can reach.
- Name a credential owner who will rotate or revoke access.
- Submit to InfoSec in the weekly InfoSec sync. Record the decision and any conditions.
- Connect only rows marked Approved. Set a review date for every row.
#The template
#Connection principles (agree once, at the top of the plan)
- Least privilege: read-only unless the approved workflow requires write.
- Clones act through named service accounts or per-user OAuth, never a shared personal login.
- Every connection has one credential owner and a review date.
- Write scopes are tied to an autonomy level. A Clone at Assist or Recommend does not hold write scopes it cannot use.
- Restricted data requires explicit InfoSec approval and a listed business justification.
- Every connection is logged in the Clone audit log.
#Connection inventory
| ID | System | Clone(s) using it | Purpose (workflow) | Method (OAuth / API key / service account / MCP / webhook) | Account model | Scopes requested | Read / Write | Data classification | Credential owner | Status | Conditions | Review date |
|---|
| CON-01 | | | | | | | | | | Proposed / Approved / Conditional / Rejected / Revoked | | |
| CON-07 | ERP (finance) | AP Matching Clone | Invoice-to-PO matching | API, service account | svc-clone-ap (dedicated) | Read: vendors, POs, receipts, invoices. Write: invoice match status only | Read + limited write | Confidential | ERP admin | Conditional | Write scope enabled only after promotion to Execute with approval | Quarterly |
#Scope justification (one block per write or Restricted-data connection)
| Field | Answer |
|---|
| Connection ID | |
| Scope | |
| Why it is needed | |
| What the Clone will never do with it | |
| Approval gate that applies (autonomy level) | |
| How misuse would be detected | |
| How to revoke within 15 minutes | |
#Role and access matrix (people)
| Clone Team Studio role | Who holds it | Can create Clones | Can connect systems | Can change skills | Can approve actions | Can view audit log |
|---|
| Org admin | | Yes | Yes | Yes | Yes | Yes |
| Builder / champion | | | | | | |
| Approver | | | | | | |
| Team member | | | | | | |
| Example: Approver | AP supervisor | No | No | No | Yes, AP Matching Clone only | Own Clone only |
#Approval workflow
| Step | Owner | Timebox |
|---|
| Connection proposed with justification | Implementation Engineer | |
| Business need confirmed | Business owner | 2 working days |
| Security review | InfoSec lead | Next weekly InfoSec sync |
| Account and scopes created | IT lead / system admin | 3 working days |
| Connection tested and logged | Implementation Engineer | 1 working day |
#Change log
| Date | Connection ID | Change | Requested by | Approved by |
|---|
| | | | |
#Good looks like
- No orphan connections. Every live connection appears in the inventory with an owner and a review date.
- Scopes match the autonomy level. A Recommend-level Clone has no write scope it does not need yet.
- Dedicated accounts. Auditors can tell Clone actions apart from human actions.
- Revocation is rehearsed. Someone has actually revoked and restored one connection during testing.
- Common mistake: approving "full access" to save time during the pilot. It is the change InfoSec will remember at promotion time.
#How Clone helps
The GRC Clone drafts the inventory from the Systems & Workflow Map, pre-fills scope justifications, and reminds credential owners before review dates. The Implementation Engineer proposes and tests each connection. In the portal, the plan is the Connections & Permissions Plan deliverable under Security & GRC; each row's status is visible to InfoSec, and new rows raised during a department rollout block the Clone Design Spec until they are approved.
#Sign-off
| Role | Name | Date | Decision |
|---|
| InfoSec lead | | | Approved / Approved with conditions / Rejected |
| IT lead | | | Accounts provisioned |
| Business owner (per department) | | | Business need confirmed |