Choose a permission mode
Decide how much Steward may do during the next request.
Choose before sending
The permission-mode selector is beside the paperclip in the message composer. Its default is Ask for approval. Select a mode before sending the request you want it to govern.
A run uses the mode it started with. If you change the selector while a run is active, the change applies to the next run, not the work already underway.
Compare the three modes
| Mode | How it works | A useful starting point |
|---|---|---|
| Read only | Steward can read available information, but cannot make changes through connected business tools. | Exploring figures or investigating an issue. |
| Ask for approval | Permitted changes are prepared as a proposal and require a decision before execution. | Updating records when you want to check the details first. |
| Automatic | Permitted changes may execute without a separate decision, unless a connection rule requires approval. | Work you are ready to let Steward carry out within your access. |
Read only concerns changes to connected tools. You can still ask for analysis and downloadable results from available information.
Permissions still apply
The chat mode controls execution, while your project role controls what you can do. Read only prevents business-tool changes. Ask for approval requires a Manager’s decision. Automatic permits supported changes for Contributors and Managers unless an approval rule requires review. Choosing a mode never changes project access.
Connection approval rules can require review even in Automatic mode. A stricter rule remains in effect.
Start with a reviewable request
When you are learning a workflow, use Ask for approval and describe the scope clearly:
Prepare updates for these three product names. Show me the proposed names before making the changes.
Open Details on the proposal to review every item. If something needs changing, select Reject and explain the revision in the chat. Steward can prepare a new proposal for that revised request.