Settings

Draft Versus Send Authority

NephAI follows this whenever the situation you described comes up.

On

All your work · must follow

Before acting, determine which action the applicable Rules allow the current authorization basis to perform. Outward authority comes only from exact-action approval or the active user-owned Automation, never from a Rule. The action classes are: - Draft only; - send routine coordination; - send a substantive reply within approved boundaries; - create or change Calendar events; - send attachments; - communicate sensitive logistics; or - communicate confidential content. If the required action exceeds the Automation's authority, prepare the action for review rather than executing it.

What this rule says

Work this covers

Global - action authorization

When it kicks in

An outward action is planned

What NephAI does

Before acting, determine which action the applicable Rules allow the current authorization basis to perform. Outward authority comes only from exact-action approval or the active user-owned Automation, never from a Rule. The action classes are: - Draft only; - send routine coordination; - send a substantive reply within approved boundaries; - create or change Calendar events; - send attachments; - communicate sensitive logistics; or - communicate confidential content. If the required action exceeds the Automation's authority, prepare the action for review rather than executing it.

When NephAI checks it

  • While it decides what to do
  • Just before it acts

Limited to

action authorization

Your test cases

2 cases you set up to check this reads correctly

If NephAI cannot satisfy it

It holds that piece of work and brings it to you rather than proceeding against this rule.

Try it out

See where this rule would take effect and how NephAI reads the cases you set up. This only shows you the result — nothing is saved, sent, or changed.

Where this rule has been used

Clashes with other rules

0

None. This rule has never asked for something another rule contradicted.

Times NephAI used it

50
  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:59 PM

  • Did not apply · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:29 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:29 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:28 PM

  • Did not apply · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:13 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:59 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:59 PM

  • Did not apply · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 10:58 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:56 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:56 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:53 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:53 PM

  • Did not apply · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 10:25 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 10:25 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:24 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:24 PM

  • Did not apply · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 10:08 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 10:07 PM