Employee seats: an AI agent with its own seat

An employee seat is a seat in your Schedchie workspace for an AI agent you run yourself, up to 5 of them on Ultra+. It drafts and schedules in the groups you pick with 36 tools, and it publishes nothing on its own: every post it schedules or edits waits for your approval.

What an employee seat is

• Employee seats are part of Ultra+, up to 5 of them, and they work during its 14-day trial.
• A seat is not a teammate. It has a name, no email and no login of its own, and it does not count against your 10 teammate seats.
• It acts as the seat, never as you. Its connection gets 36 tools, against 75 for a full connection of your own.
• You bring the agent. Schedchie gives it a seat with a hold on it; it does not run one for you.

Its tools, area by area

Off limits to a seat

• Publish anything without your approval.
• Approve, reject or retry a post, its own included.
• Delete anything: posts, media, notes or presets.
• Edit or reschedule a post it did not write: yours, a teammate’s or another seat’s.
• Put a post in your queue slots or move the queue. It schedules at fixed dates and times only.
• Reply, like or hide anything in public. It reads comments and mentions, and answers none of them.
• Connect or disconnect accounts, or create, rename or move groups.
• Manage the team, client review links or client connect links.
• See billing, notification settings or X credits.
• See a group you did not give it, or any other workspace.
• Create connection tokens or API keys.

A call outside its tools answers that it is not available to an employee seat and that the workspace owner does it in Schedchie.

The approval hold

Every post a seat schedules or edits is held, the same way a teammate’s post is held when you require approval. For a seat the hold is fixed: there is no setting that turns it off.

• Held posts wait under Waiting for your approval on Dashboard → Team, beside your teammates’ posts, and the email you get names the seat.
• Approve, Edit & approve, Reschedule and Reject work as they do for a teammate: see post approvals.
• A post the seat reschedules is held again, so an approved post never moves to a new time without you.
• Reject with a note and the agent reads it: get_post returns it as Rejected by the owner: followed by your note. When the agent edits the post, the edit waits for you again.

Creating a seat

1. 1

   Open Agents

   Go to Dashboard → Agents. Your agent fleet shows how many seats are in use, what each one has waiting for your approval and when it was last active.
2. 2

   Press New agent seat and name it

   Pick a name you will recognise in the approval list and the email, up to 60 characters.
3. 3

   Pick its groups

   All groups, or Only these groups and tick the ones it works in. The groups are set once: to change them, revoke the seat and create a new one.
4. 4

   Press Create seat

   The seat appears in the list with its groups. Connect the agent next.

Connecting the agent

The agent connects to the employee address:

https://mcp.schedchie.com/employee

It is not the address your own assistant uses (https://mcp.schedchie.com/mcp). The employee address refuses your own sign-in, so whatever connects there runs as a seat.

Sign in and pick the seat

Add the address as a connector in the agent’s client. Sign-in happens on Schedchie: sign in with your own email and password, pick the seat on the next screen and press Connect this seat. The client receives the seat’s credential, never yours.

Or paste a seat token

For a client that takes a token instead, or if you sign in to Schedchie with Google (the employee sign-in takes email and password only), press Create token on the seat’s row and give the token to the client with the employee address.

• The token is shown once. Copy it when it appears and treat it like a password.
• It works for 30 days. Revoking the seat stops it earlier.
• It acts as the seat, with the same groups and the same hold.

An API key bound to a seat

On Ultra+, an API key can act as a seat instead of as you. On Dashboard → AI assistants, press New key in the API keys card, tick its permissions and choose the seat under Bind to employee seat. The key then works as that seat: its groups, its refusals, every post it schedules or edits held. The API itself is documented at schedchie.com/developers.

• API keys come after your first paid invoice, not during the trial. Employee seats work in the trial.
• Ultra+ holds up to 10 active API keys, seat-bound ones included.
• The permissions ticked on the key narrow what the seat can do through it. They never add to it.

Revoking a seat

Press the bin button on the seat’s row in Dashboard → Agents and confirm. Every token and API key bound to the seat stops working within a minute, and it cannot be undone.

• Posts the seat already scheduled stay on your calendar. Held ones still wait for your decision.
• A revoked seat stays in the list, marked Revoked.
• Off Ultra+, seats stop working, and you can still revoke them.

Ceilings

Each token or key a seat holds has its own hourly budget. An open whose session goes on to make a tool call is given back, so only opens that run nothing count. How the plans compare is in plans, trial and cancellation.