Skip to main content

Members and roles

Access in FYAI works at two levels, matching organisations and projects:

  • An organisation role (Owner, Admin or Member) decides who can manage the organisation itself.
  • A project role (Admin, Editor, Viewer or Runner) decides what someone can do inside a project.

On top of project roles, run access lets a project Admin allow a low-privilege member to launch specific workflows or agents.

Organisation roles​

Every organisation has three roles.

RoleCan do
OwnerEverything an Admin can, plus delete the organisation. The person who creates an organisation is its owner.
AdminInvite and remove members, change members' roles, cancel pending invitations, create projects, edit the organisation, manage Built-in Tools, and change the subscription plan. Owners and Admins also have full Admin rights in every project in the organisation.
MemberWork in the projects they're a member of, with the rights their project role gives them.

You can't give anyone a role higher than your own, and you can't change or remove someone who outranks you.

Project roles​

RoleShown asCan do
project:adminAdminFull control of the project, including its members, run access, settings (such as Risk Appetite), deleting the project and promoting to other projects.
project:editorEditorCreate, change and run anything in the project.
project:viewerViewerList and read resources. Can't create, change or run anything unless given run access.
project:runnerRunnerLaunch only the workflows and agents they've been given run access to. Can't read or change configuration.

Organisation Owners and Admins are treated as project Admins everywhere in their organisation, whether or not they're listed as project members. Someone with no role in a project can't see it.

Invite people to your organisation​

You need to be an Owner or Admin of the organisation.

  1. Go to Settings → Organization and select the organisation.
  2. Under Invite Members, enter one or more email addresses, separated by commas.
  3. Select Invite.

Each person gets an email:

  • No FYAI account yet: the email contains an enrolment link. When they sign up and sign in, they join your organisation automatically.
  • Existing FYAI account: the email points them to FYAI, where they accept the invitation.

Invitations expire after 7 days. New members join with the Member role; change it afterwards if needed. Inviting the same address again replaces the earlier invitation.

Pending invitations​

Owners and Admins see a Pending invitations list under the invite box, with each address and its expiry date. To withdraw one, select the cross (Cancel invitation) and confirm. There's no resend button; invite the address again to send a fresh invitation.

Accepting an invitation​

If you already have an account, a badge appears on your avatar when you have an invitation. Open the avatar menu: the Invitations section shows each organisation and who invited you. Select Accept or Decline.

Accepting adds you to the organisation but doesn't switch you to it. Switch from Settings → Organization or the project switcher.

Manage organisation members​

The Team Members list in Settings → Organization shows everyone in the organisation, with chips for the Owner and anyone still Invited.

  • Change a role: choose a new role from the drop-down next to the member.
  • Remove a member: select the bin icon (Remove member) and confirm.

The owner's role can't be changed and the owner can't be removed. Only Owners and Admins can make these changes.

Add people to a project​

You need to be the project's Admin, or an Owner or Admin of the organisation.

  1. Go to Settings → Projects and select the project.
  2. Under Members, enter the person's email address.
  3. Choose a role: Admin, Editor, Viewer or Runner.
  4. Select Add.

The person must already have an FYAI account; invite them to the organisation first if they don't. They get an email telling them they've been added.

To change a member's role, use the drop-down on their row. To remove them, select the bin icon (Remove member).

Run access​

Run access lets a Viewer or Runner launch particular workflows or agents without being able to edit anything. Editors and Admins can already launch everything, so run access only matters for the two lower roles.

  1. In Settings → Projects, select the project.
  2. On the member's row, select the key icon (Manage run access).
  3. In Run access, choose a Type (Workflow or Agent) and a Resource, then select Grant.
  4. Repeat for each item, then select Close.

Granted items appear as chips; remove a chip to revoke that grant. Run access doesn't give the member rights to edit or chat.

note

The Resource list shows the workflows and agents in your current project. Switch to the project you're managing before granting run access.

API keys and service accounts​

Programs that call FYAI authenticate with an API key or a service account rather than a person's login. Each carries a project role, so the same rules apply.

  • API keys (Settings → My account → API Keys) belong to you and are tied to your current organisation and project. When you create one, you pick its access: Run, Read, Write or Admin, which correspond to Runner, Viewer, Editor and Admin. You can't create a key with more access than you have yourself. The key is shown once. See Platform API.
  • Service accounts use OAuth2 client credentials. The Service Accounts section is currently only shown to FYAI platform staff; contact FYAI if you need one.

FYAI platform staff​

FYAI staff belong to a special administrative organisation. Members of it can act across every organisation and see the Platform administration group in Settings. See Platform administration.