Step 7: Member Configuration
Step 7 configures each member. You set only what is unique to the job. Everything else is inherited from the Force. The same form opens when you Add a member in step 6 and when you Edit a member later.
Chips at the top switch between members. Switching with unsaved changes asks Discard unsaved changes?. The lead line reads Member N of M. After you save a member, the wizard moves to the next one, and to step 8 after the last.
The form has four tabs. Identity and Job show a green check once they are filled in. The action row holds the save button (Bring (name) on when hiring, Save changes when editing), Next: (tab), and Cancel (Back to setup inside the wizard). The save button stays disabled until a name is entered.
Identity tab
Choose a starting point
Pick a persona card to pre-fill the member, or choose Start from scratch.
Screenshot placeholderScreenshot to add: The Identity tab with persona cards and Start from scratch. Introduce them
Enter a Name (required, e.g.
MayaorDev). Initials for the avatar are generated automatically.Pick a role
Under Role on the team, choose Manager (marked Recommended), Worker, Synthesizer, Critic or Actor. Each card's (i) explains the job and what happens without one. Manager, Synthesizer, Critic and Actor are singular: a team uses only one, whoever was hired first. Choosing one that is held clears it from the previous holder.
Job tab
Point them at what to read
Under Point them at what they should read, use Knowledge bases (placeholder "Choose knowledge bases…") to grant access. Members only ever see what you can see. The Force's connected knowledge bases are pre-selected. If the Force has no project it says Needs a project.
Write the job description
In Job Description / Instructions, write what you would tell a new hire on their first day. It is added to every turn the member takes. Optional.
Screenshot placeholderScreenshot to add: The Job tab with the Knowledge bases selector and Job Description textarea.
Access tab
Choose a tool access mode
Tool access is a four-way control. The default is Auto.
Mode What the member gets Auto Core tools plus whichever allowed systems the request needs each turn (default) Essential Core tools only, plus any Studio tool you add. No connected systems Selected Core tools plus only the systems and tools you pick, the same set every turn All Everything you allow, every turn. An empty list means everything the team is connected to Screenshot placeholderScreenshot to add: The Access tab showing the four tool access modes. Pick systems
Unless the mode is Essential, choose Every system this team is connected to (default) or Only the ones I pick, then choose from Systems. For each picked system, set How much of each system: Read only, Read and change, or Read, and draft changes for approval. Systems that only offer lookups have no such choice.
Pick Studio tools
Use Tools (placeholder "Choose specific tools…") to add specific Studio tools. They are opt-in and carry their own credentials.
Choose skill access
Skill access has the same four modes. Unless Essential, choose Any published skill or Only the ones I pick, then select from Skills.
Choose which account they sign in as
If the owner has two or more connections for a provider, a per-provider selector appears. It decides whose mailbox or workspace the member uses, not what they may do with it.
Authority tab
Set permanent limits
Under What they must never do, tick any of:
- Never writes anywhere
- Never sends email or messages
- Never deletes anything
These are hard limits, stronger than trust or any instruction. Ticking the first makes the other two redundant and disables them. None are on by default.
Screenshot placeholderScreenshot to add: The Authority tab with the three permanent limit checkboxes. Choose the model
Under Runs on, click Change to open the Models drawer, or leave the default (placeholder "Use their default model"). If you are not the Force owner you may also choose whose AI key pays: the owner's, or My AI key. The owner's option is disabled if they have not allowed teammates to hire on it.
Set the time budget
Under Runs for up to, set how long the member gets per step before timing out. Type a value, switch between seconds and minutes, use a preset (5 min, 10 min, 15 min, 30 min, 1 hour) or the slider. The range is 300 to 3600 seconds, default 600. Out-of-range values are adjusted on save.
Choose starting trust
Set Starting trust on the three-position track: Shadowing (default), Learning or Trusted. Trust never grants systems or lifts a limit.
| Field | Type | Required | Default | What it does |
|---|---|---|---|---|
| Name | Text | Yes | — | Shown on the roster and in runs. |
| Role on the team | Card picker | No | Manager (first), Worker (later) | Decides which steps the member is dispatched to. |
| Knowledge bases | Multi-select | No | Force knowledge bases | What the member may read. |
| Job Description / Instructions | Text area (3 rows) | No | — | Added to every turn the member takes. |
| Tool access | Auto / Essential / Selected / All | No | Auto | Which tools and systems each turn can use. |
| Skill access | Auto / Essential / Selected / All | No | Auto | Which skills each turn can use. |
| What they must never do | Checkboxes | No | None | Permanent limits. |
| Runs on | Model picker | No | Default model | Blank uses the default of whoever pays. |
| Runs for up to | Number plus presets | No | 600 seconds | 300 to 3600 seconds. |
| Starting trust | 3-step track | No | Shadowing | Called Trust when editing. |
Saving, errors and conflicts
- Hiring succeeds with a toast saying the member is on the team and starts at their trust level. Editing shows Saved changes to (name).
- Hiring is blocked (HTTP 402) when no model or AI key is configured. The message includes a link to fix it.
- If someone else edited the same member, a conflict panel lets you choose Keep mine, Take theirs or Merge for each field. You cannot save until every field is resolved.
- When editing a member created from a persona, Re-sync from persona refreshes them but resets trust to Shadowing.