Organization & access

List the organization's roles and what each grants. A role is held at the whole organization, a Client or one Job.

See what one role grants and how many assignments hold it.

See what editing a role, or deleting it, would change: the capabilities added and lost, how many people hold it and how many invitations not accepted yet hold it, the Jobs it reaches, and the Human Review steps that name it when it would no longer decide. Admins only.

List role assignments on a Job (anyone who sees it), or, for admins, on a Client, of one person, or across the organization. Anyone may list their own.

Give a member of the organization a role on a Job, on a Client, or (admins) organization-wide. You can give only roles whose capabilities you hold there yourself.

Take a role away from someone where they hold it. They lose what it grants there unless another role gives it. Shows what they lose before it is done.

Give a role to someone by email. A member gets it at once; anyone else is emailed an invitation to join the organization and gets the role when they accept.

List where Invyte's agents hold a role in the organization (organization-wide, a Client or a Job) and, for each working agent (pipeline, delivery, communication, intake, sourcing, orchestrator, workflow), the modes set at each place: off, suggest, ask or auto per effect. Unset modes inherit the next wider place; unset everywhere is ask. Also whether each agent is paused, its monthly budget and this month's spend. Admins only.

Give Invyte's agents a role organization-wide, on every Job of a Client, or on one Job, replacing the role they hold there; or take their role there away (roleId null). roleId `admin`, organization-wide only, gives them an admin's reach except organization settings (profile, members, roles, their own access, approvals, integrations). Every working agent shares it and still calls only its own work (Intake drafts and publishes Jobs, Sourcing finds people, and so on); with no role anywhere they can do nothing in the organization. Modes set at that place stay. Admins only.

Pause one of Invyte's working agents in the organization (it is refused everything at once and starts no work) or resume it, and set its monthly model budget in USD (null for Invyte's default). Admins only.

Set how one of Invyte's working agents acts where their role reaches: per effect (write, outside, destructive) off, suggest (drafts only), ask (waits for a person's approval) or auto (commits and reports). The most specific place wins: Job, then Client, then organization. A mode never grants anything the role does not; destructive effects never go past ask. Admins only.

See how the organization appears to candidates: job board address, tagline, website, locations, industries, brand colour and logo, and whether Jobs may be listed on Google for Jobs.

Change how the organization appears to candidates on its job board and in emails: tagline, website, locations, industries, brand colour, or the job board address (changing the address breaks links already shared). Admins only. Shows each change before it is saved.

Allow the organization's Jobs to be listed in Google search (each Job still needs its own 'List on Google'), or take every Job off Google. Needs a job board address first. Admins only.

A logo is a file upload, so it happens in Invyte: returns the link to the organization profile, where an admin uploads it (PNG, JPG or WebP, up to 1 MB) and saves. Admins only.

List the organization's members, newest first, 100 a page (`nextCursor` for more): name, email, whether each is an admin, and when they joined. What a member may do is their roles (access.listAssignments).

Make a member an admin (everything, on every Job, and the organization's settings) or an admin a member (only the roles they hold). Not for yourself. Admins only. Changes who may do what across the organization, so it shows the change and waits for your go-ahead.

Remove a member from the organization: they lose access to it and every role they hold here. Not for yourself. Admins only. Shows who and what goes before it is done.

List invitations to join the organization, newest first, 100 a page (`nextCursor` for more): who, when, and whether each is pending, accepted, expired or revoked. Admins only.

Revoke a pending invitation so its link no longer works; any role held for the invitee goes with it. To invite them again, send a new invitation. Admins only.

List people waiting to join the organization, with the level they asked for. Admins only.

Approve a join request (they become a member, or an admin if they asked for that, and can sign in to the organization) or decline it. Admins only. Shows who and at what level before it is done.

Add a role to the organization with the capabilities it grants. It reaches nobody until it is given (access.assign). Admins only.

Rename a role, change its description, or set what it grants. Everyone holding it gains or loses those capabilities wherever they hold it; its review says who loses what, and it waits for a go-ahead. Can be undone (access.undoRoleChange). Admins only.

Delete a role: everyone holding it loses it, everywhere. Undoing it later brings back only assignments whose person, Job or Client still exists. Admins only. Shows who loses what before it is done.

Put one of the four starting roles (Team Lead, Hiring Manager, Recruiter, Analyst) back to its default name, description and capabilities. It can take access away, so it waits for a go-ahead. Can be undone. Admins only.

The organization's role changes, newest first: who changed which role, what it added or removed, and whether it can still be undone. Admins only.

Undo a role's latest change: an edit or restore puts the role back as it was, a delete brings the role back with the assignments that still apply, and a create deletes a role nobody holds yet. An undo can't itself be undone, and it can take access away, so it waits for a go-ahead. Admins only.