Book a build call
Back to Help
Guide

Set what a seat may do: grant limits in plain words

4 min read

When you seat an administrator on your Command Center, it gets a chair, not a blank check. Before it can hand work to anyone, you give it a grant: three limits that say how much it may spend on one goal, how much in one day, and how far down it may pass work. This guide walks the one page where those limits show, what each one means, what happens when work reaches one, and where you change them. For the wider picture of the Harness, read One face, many brains.

Where the limits show

Open the Command Center and look at the Your administrator card on the left (at the top on a phone).

Before you authorize it, the card says not authorized yet and spells out the offer in one sentence: once you authorize it, it can spend up to 100 credits a goal and 1,000 credits a day, and it can pass work two levels down. It also tells you that you can take it back at any time. Nothing is granted until you press Authorize my administrator.

After you press it, the badge reads authorized to act and the same card shows the live grant as one sentence, for example: it can spend up to 100 credits a goal and 1,000 credits a day, and it can pass work two levels down. That sentence is read from your grant, so when you change a limit, the sentence changes with it.

What each limit means

  • A goal. A goal is what you type under Hand over a goal. The first number is the most your administrator may plan to spend on that one goal, counted in credits, the same credits the Credits tile on the same page counts.
  • A day. The second number is a ceiling for the day. Your administrator plans every goal against the smaller of the two numbers, so a day ceiling set lower than the goal ceiling tightens every goal.
  • Levels down. Your administrator can hand pieces of a goal to the seats under it, and they can hand work on again. The depth says how many levels down that may go. It is never more than three, and at zero it cannot pass work on to anyone.

What happens when work reaches a limit

Your administrator makes a plan before anyone does any work, and the plan is checked against the grant first. It never spends past a limit and settles up later:

  • If the plan costs more than the grant allows, nothing starts. The page tells you: That plan costs more than the grant allows — it is waiting for your approval. The goal counts under Waiting on you. You can raise the limit and hand the goal over again, or hand over a smaller goal.
  • If the depth leaves no room to pass work on, the goal is refused and the page says: Your administrator refused this goal — nothing was handed out and no seat did any work. The reason sits next to it. A seat further down that tries to pass work past the depth is refused too, and that piece is not run.
  • If a limit is set to 0, or the grant has passed its end date, your administrator cannot take a goal at all until you set it again. A 0 never means unlimited.

Change the limits

The limits live on the detail view. Press Detail view at the top of the Command Center, or open your organization directly.

  1. Find the Delegation grants card. Each grant shows its depth, task ceiling and day ceiling in one line; tap it to open the form.
  2. Set Per-task ceiling (the per-goal number), Per-day ceiling and Depth (max 3). Leave Expires empty for a grant with no end date, or give it a date and time when it should stop.
  3. Type why you are changing it in Reason (required). Every change is kept with its reason.
  4. Press Save grant. The page says Grant updated. and the next goal your administrator takes is held to the new limits.

A depth above three is not saved: the page tells you the depth must stay within 0 to 3. There is no switch that turns the limits off: every grant has a ceiling for a goal, a ceiling for a day and a depth.

Stop everything at once

If you want work to stop rather than shrink, the same detail view has Pause next to every seat and department in the org chart, and Pause all for the whole organization. A pause takes effect on the next command, and a paused seat or department shows Resume so you can start it again.

Still stuck?

The longer documentation covers models, voice, knowledge, and workflows in depth.

Open the documentation