Discuss your stack

A permission brief your team can use.

See what the brief contains, then start your own draft. No account or email.

What this brief covers

Plan up to ten actions, two alternative sets per action and six conditions per set. These limits apply to the brief, not to the platform. Combine amount ranges, independent checks and operating state. This form sketches one workflow; it is not the G-14 configuration interface. The brief does not issue permission, check real-world conditions or run a system.

Your starting draft was prefilled from the fictional production change example. These action names and roles are starting points, not approvals or an issued permit. Edit the plan for your own process.

What your team gets.

For example: release a supplier payment, with a person approving each time and three conditions that must all hold.

Fictional example. Planning, not permission.

Download this sample permission brief (PDF)

Read the fictional supplier-payment example

Release a supplier payment.

Ask a person each time.

All of these must hold.

  • More than USD 5,000 and less than USD 10,000.
  • The bank details have been confirmed by an independent call-back.
  • The supplier account is still active when the payment is made.

Exactly USD 5,000 or USD 10,000 does not qualify.

Example context and open questions

System it affects: Vendor record in the ERP.

Still to define: the approval role, scope, time window, uses and escalation. Who owns each input, when is it checked, and what happens if it cannot be confirmed?

Loading the example doesn’t submit your draft. The brief is a planning document for your team; it doesn’t switch on any rule or grant any permission.

Your workflow, in plain language.

Describe what may happen, what must be true and what stays out.

Review the permission brief

For example: a business record, software repository or deployment target.

Actions and permissions

Start with one action. Add only the actions this workflow needs.

01Open or update the incidentWithin a standing permit

This requests a standing-permit route. No permit is issued here.

A blank action role uses the workflow role if one is entered. Otherwise the brief says “To be confirmed”.

What must be true?

Every condition here must hold (AND).

Scope, time, uses and the human decision apply in every case.

All of these must hold

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Up to 6 conditions in a set.

Each set must be complete on its own. Choosing a set does not drop scope, time, uses or the human decision.

If no complete set of required conditions can be confirmed, the action does not run. This is the planned rule. The form does not check these requirements.

Scope, time, uses and escalation

Scope
Not specified
Time window
Not specified
Uses
Not specified
Escalation
Not specified
Edit these terms

Requested terms are for this action alone; uses are not shared with other actions. Anything left blank is marked “To be confirmed”.

Uses, if specified, must be a whole number from 1 to 100000, without leading zeros.

Describe what your team should do when requirements cannot be confirmed. This is not permission to bypass the rule.

Removing an action permanently deletes its entered details from this unsaved draft.

02Change the log levelWithin a standing permit

This requests a standing-permit route. No permit is issued here.

A blank action role uses the workflow role if one is entered. Otherwise the brief says “To be confirmed”.

What must be true?

Every condition here must hold (AND).

Scope, time, uses and the human decision apply in every case.

All of these must hold

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Up to 6 conditions in a set.

Each set must be complete on its own. Choosing a set does not drop scope, time, uses or the human decision.

If no complete set of required conditions can be confirmed, the action does not run. This is the planned rule. The form does not check these requirements.

Scope, time, uses and escalation

Scope
Not specified
Time window
Not specified
Uses
Not specified
Escalation
Not specified
Edit these terms

Requested terms are for this action alone; uses are not shared with other actions. Anything left blank is marked “To be confirmed”.

Uses, if specified, must be a whole number from 1 to 100000, without leading zeros.

Describe what your team should do when requirements cannot be confirmed. This is not permission to bypass the rule.

Removing an action permanently deletes its entered details from this unsaved draft.

03Scale the serviceAsk a person each time

This is a planned approval step, not an approval granted here.

A blank action role uses the workflow role if one is entered. Otherwise the brief says “To be confirmed”.

What must be true?

Every condition here must hold (AND).

Scope, time, uses and the human decision apply in every case.

All of these must hold

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Up to 6 conditions in a set.

Each set must be complete on its own. Choosing a set does not drop scope, time, uses or the human decision.

If no complete set of required conditions can be confirmed, the action does not run. This is the planned rule. The form does not check these requirements.

Scope, time, uses and escalation

Scope
Not specified
Time window
Not specified
Uses
Not specified
Escalation
Not specified
Edit these terms

Requested terms are for this action alone; uses are not shared with other actions. Anything left blank is marked “To be confirmed”.

Uses, if specified, must be a whole number from 1 to 100000, without leading zeros.

Describe what your team should do when requirements cannot be confirmed. This is not permission to bypass the rule.

Removing an action permanently deletes its entered details from this unsaved draft.

04Turn a feature flag offAsk a person each time

This is a planned approval step, not an approval granted here.

A blank action role uses the workflow role if one is entered. Otherwise the brief says “To be confirmed”.

What must be true?

Every condition here must hold (AND).

Scope, time, uses and the human decision apply in every case.

All of these must hold

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Up to 6 conditions in a set.

Each set must be complete on its own. Choosing a set does not drop scope, time, uses or the human decision.

If no complete set of required conditions can be confirmed, the action does not run. This is the planned rule. The form does not check these requirements.

Scope, time, uses and escalation

Scope
Not specified
Time window
Not specified
Uses
Not specified
Escalation
Not specified
Edit these terms

Requested terms are for this action alone; uses are not shared with other actions. Anything left blank is marked “To be confirmed”.

Uses, if specified, must be a whole number from 1 to 100000, without leading zeros.

Describe what your team should do when requirements cannot be confirmed. This is not permission to bypass the rule.

Removing an action permanently deletes its entered details from this unsaved draft.

05Roll the configurationAsk a person each time

This is a planned approval step, not an approval granted here.

A blank action role uses the workflow role if one is entered. Otherwise the brief says “To be confirmed”.

What must be true?

Every condition here must hold (AND).

Scope, time, uses and the human decision apply in every case.

All of these must hold

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Up to 6 conditions in a set.

Each set must be complete on its own. Choosing a set does not drop scope, time, uses or the human decision.

If no complete set of required conditions can be confirmed, the action does not run. This is the planned rule. The form does not check these requirements.

Scope, time, uses and escalation

Scope
Not specified
Time window
Not specified
Uses
Not specified
Escalation
Not specified
Edit these terms

Requested terms are for this action alone; uses are not shared with other actions. Anything left blank is marked “To be confirmed”.

Uses, if specified, must be a whole number from 1 to 100000, without leading zeros.

Describe what your team should do when requirements cannot be confirmed. This is not permission to bypass the rule.

Removing an action permanently deletes its entered details from this unsaved draft.

06Change the database schemaNever in this workflow

This action never runs in this workflow. Nothing added below changes that. Existing details stay visible and are kept in the brief as notes.

A role entered here is kept as a note. It cannot make this action run.

Retained condition notes

Notes do not change this workflow's exclusion.

Notes from set 1

No condition notes entered.

Up to 6 conditions in a set.

Retained scope, time, use and escalation notes

Scope note
Not specified
Time window note
Not specified
Use budget note
Not specified
Escalation note
Not specified
Edit retained notes

Anything entered here is kept as a planning note. This action stays excluded from the workflow.

Uses, if specified, must be a whole number from 1 to 100000, without leading zeros.

Describe what your team should do when requirements cannot be confirmed. This is not permission to bypass the rule.

Removing an action permanently deletes its entered details from this unsaved draft.

Up to 10 actions. Your draft is not autosaved.

Read the permission brief.

A descriptive review of the current draft, not a simulation or an approval.

Review the whole brief before you download

Permission brief. Draft for discussion.

Workflow
Production change
System or asset it affects
service
Usual approval role
on-call lead

1. Open or update the incident

Within a standing permit

Approval contact, if needed: on-call lead

Scope, time, uses and the human decision apply in every case.

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Requested scope
To be defined
Requested time window
To be defined
Requested uses
To be defined
Planned escalation note
To be defined

Still to define: scope, number of uses, time window and what happens if conditions can’t be confirmed.

These are planning requirements and notes. This page does not check them.

2. Change the log level

Within a standing permit

Approval contact, if needed: on-call lead

Scope, time, uses and the human decision apply in every case.

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Requested scope
To be defined
Requested time window
To be defined
Requested uses
To be defined
Planned escalation note
To be defined

Still to define: scope, number of uses, time window and what happens if conditions can’t be confirmed.

These are planning requirements and notes. This page does not check them.

3. Scale the service

Ask a person each time

Planned approval role: on-call lead

Scope, time, uses and the human decision apply in every case.

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Requested scope
To be defined
Requested time window
To be defined
Requested uses
To be defined
Planned escalation note
To be defined

Still to define: scope, number of uses, time window and what happens if conditions can’t be confirmed.

These are planning requirements and notes. This page does not check them.

4. Turn a feature flag off

Ask a person each time

Planned approval role: on-call lead

Scope, time, uses and the human decision apply in every case.

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Requested scope
To be defined
Requested time window
To be defined
Requested uses
To be defined
Planned escalation note
To be defined

Still to define: scope, number of uses, time window and what happens if conditions can’t be confirmed.

These are planning requirements and notes. This page does not check them.

5. Roll the configuration

Ask a person each time

Planned approval role: on-call lead

Scope, time, uses and the human decision apply in every case.

No conditions yet. The planned rule still requires the scope, time, uses and human decision; if required conditions can’t be confirmed, the action doesn’t run.

Requested scope
To be defined
Requested time window
To be defined
Requested uses
To be defined
Planned escalation note
To be defined

Still to define: scope, number of uses, time window and what happens if conditions can’t be confirmed.

These are planning requirements and notes. This page does not check them.

6. Change the database schema

Never in this workflow

This action never runs in this workflow. Nothing added below changes that.

Scope note
To be defined
Time window note
To be defined
Use budget note
To be defined
Escalation note (non-operative)
To be defined

These are planning requirements and notes. This page does not check them.

A brief your team can use.

The PDF is a planning document to share or attach to an implementation discussion. It grants no permission.

Downloading sends these planning details to G-14 to create the PDF. Do not include customer details, credentials or secrets. This planner does not autosave your draft.

How the PDF handles your text

The brief turns line breaks and tabs into spaces and trims outer spaces. Characters the PDF cannot print are reported rather than replaced.

Downloading submits your draft to generate the document. The generator does not save or forward your draft. That describes the generator, not server logs or retention; see privacy and data handling.

Take it to your team.

Share the brief with your team. If you’d like to discuss an integration with G-14, email hello@g14.ai. You can attach the brief to start with the actions, conditions and open questions you have set out.

For the wider capability suite, read Platform. For the host responsibilities and integration choices, read Developers.