Routing
Decide who gets assigned each incoming request.
Routing decides which approver a request lands with. Every
workspace starts with a ready-made default path that sends requests to
the built-in approver role, so agents can submit requests before
you configure anything. Agents can also address a specific approver
directly with recipientUserId.
Per request type you set the assignee: a named person or a role. Role assignment draws from the people holding that role (see People & roles).
The Routing page also shows the assignment state of live requests — handy for spotting requests sitting unrouted or unclaimed. Routing changes apply to new submissions; requests already assigned keep their assignee until reassigned.
A request can't be created if its routing resolves to no assignee —
the agent gets bad_request. Keep routing configured for every
request type you expect agents to use.