S14 · Pipeline skill
Set access rules
Define team access, review rule changes and test allowed and denied requests.
Role scope definition + policy version approval + access verification
- Pipeline
- 4 steps
- Human review
- 2
- Components
- 6
01Pipeline
Base pipeline
Ordered steps. Each consumes the previous output; review gates hold until a person accepts.
- Starts from
- Team roles, service catalog and access requirements
- Delivers
- Access acceptance decision and rollback version
Review contract
People decide at review gates; components supply data, drafts or review surfaces. Unaccepted outputs do not advance.
Integration note
Test identity, prompt and tool-proxy policy layers separately and preserve pending approvals on later requests.
- 01
Define access scope
- Input
- Team roles, service catalog and access requirements
- Output
- Role and request policy drafts
- Workspace and agent access governanceTeam role configuration + service access scopes
- Prompt registry, cache and semantic policiesPrompt template management + intent and guardrail checks
- 02
Validate and review changes
Human review- Input
- Role and request policy drafts
- Output
- Human-approved policy version
Decided byAssigned reviewer or requesting user
- Versioned gateway policy rolloutPolicy validation and diff review + publication and rollback
- Gateway plugins and configuration migrationPolicy extension loading + versioned config validation and rollback
- 03
Apply access rules
- Input
- Human-approved policy version
- Output
- Allowed, denied or pending-approval requests under policy
- Policy-controlled MCP gatewayTool-call proxying + endpoint and environment policy limits
- Governed provider and tool execution gatewayRequest scope and budget checks + approval and idempotent calls
- 04
Review request evidence
Human review- Input
- Allowed, denied or pending-approval requests under policy
- Output
- Access acceptance decision and rollback version
Decided byAssigned reviewer or requesting user
- Workspace and agent access governanceTeam role configuration + service access scopes
- Versioned gateway policy rolloutPolicy validation and diff review + publication and rollback
02Industry versions
Industry versions
Government & public services Transferable use Set consultation-tool access by desk and department responsibilities and test permitted and denied requests before release.
Adaptation Connect organization identity and actual document permissions; prompt wording alone cannot enforce access.
- 01
Define desk and department scopes
- Input
- Department responsibilities, document catalog and access boundaries
- Output
- Role and service-access drafts
- Workspace and agent access governanceTeam role configuration + service access scopes
- Prompt registry, cache and semantic policiesPrompt template management + intent and guardrail checks
- 02
Review access-rule changes
Human review- Input
- Role and service-access drafts
- Output
- Approved access-rule version
Decided byAssigned reviewer or requesting user
- Versioned gateway policy rolloutPolicy validation and diff review + publication and rollback
- Gateway plugins and configuration migrationPolicy extension loading + versioned config validation and rollback
- 03
Apply consultation-tool scopes
- Input
- Approved access-rule version
- Output
- Allowed, denied or pending-approval outcomes
- Policy-controlled MCP gatewayTool-call proxying + endpoint and environment policy limits
- Governed provider and tool execution gatewayRequest scope and budget checks + approval and idempotent calls
- 04
Officer reviews request evidence
Human review- Input
- Allowed, denied or pending-approval outcomes
- Output
- Acceptance decision and rollback version
Decided byAssigned reviewer or requesting user
- Workspace and agent access governanceTeam role configuration + service access scopes
- Versioned gateway policy rolloutPolicy validation and diff review + publication and rollback
03Parameters
Parameters
From the pack’s params.schema.json. Choose values to build a synthetic request.
skills/_pipelines/team-access-rules/params.schema.json
{
"synthetic": true,
"run_id": "synthetic-example",
"locale": "en",
"industry": "base",
"adapter_mode": "local",
"records": [
{
"id": "synthetic-record-1",
"synthetic": true,
"text": "Synthetic observation A: a draft needs review."
},
{
"id": "synthetic-record-2",
"synthetic": true,
"text": "Synthetic observation B: retain the unresolved question."
}
],
"decisions": {}
} 04Member components
Member components
-
Workspace and agent access governance
Team role configuration + service access scopes
Working 1 pipeline -
Prompt registry, cache and semantic policies
Prompt template management + intent and guardrail checks
Working 1 pipeline -
Versioned gateway policy rollout
Policy validation and diff review + publication and rollback
Working 1 pipeline -
Gateway plugins and configuration migration
Policy extension loading + versioned config validation and rollback
Working 2 pipelines -
Policy-controlled MCP gateway
Tool-call proxying + endpoint and environment policy limits
Working 1 pipeline -
Governed provider and tool execution gateway
Request scope and budget checks + approval and idempotent calls
Working 1 pipeline
05Skills pack
Skills pack
Runnable reference on synthetic fixtures with tests. Domain contracts, services and approvals still need integration.
team-access-rules-1.0.0.zip
Contains SKILL.md, pipeline.json, params.schema.json, runner, tests, fixtures, integration checklist and sources.
Synthetic workflow reference; service integration pending
Download · 17KBSHA-256 9bf0f65cd1f7461aab36cc6356c72e92fcf2d17d38a9b4ffb047c3534df966b1