Opening Settings
Pick the target project from the left sidebar of the console, then click 'Settings' in the project header to open the project settings screen. You land on the General tab by default.
Layout
Tab navigation is on the left, and the selected tab's content is rendered on the right. Each tab is enabled or disabled based on your role and permissions — visiting a tab you cannot access by URL redirects you to one you can.
Edit project metadata (name and description), and — for the project Owner only — delete the project.
Review the project members and their roles, and handle invitations, role changes, removal, and leaving.
Issue and revoke API keys that Claude Code uses to talk to the project.
General
Edit the project's metadata. Changes only apply after pressing 'Save', and once saved they are immediately reflected in the sidebar and visible to every project member.
The display name used to identify the project. It appears in the sidebar, console header, and report titles, so pick something the team can recognize at a glance.
An optional short paragraph describing the project's purpose or scope. It can be left blank — its main use is to help new members ramp up quickly.
The 'Save' button is only enabled when the name is non-empty. On success, a toast confirms the update and the project list is reloaded.
Only the project Owner sees the 'Delete project' button. Clicking it opens a confirmation modal that requires typing the exact project name to enable deletion. A deleted project's timeline, sessions, reports, and API keys cannot be recovered, so use this with care.
Members
Review and manage every member of the project from one screen. Management actions like the invite policy toggle, pending invitations, role changes, and removal are restricted to Admin and above.
By default only Admin+ can send invites, but this toggle lets regular members send invite emails as well. It is rendered as an Admin-only card.
Enter an email and press 'Invite' to send the appropriate invitation email depending on whether the address has an account. If the toggle is off, regular members see a notice that only admins can invite.
Lists invitations that have not yet been accepted along with the time they were sent. Each row has a 'Cancel' button that revokes the invitation immediately.
Admins can move other members between PROJECT_ADMIN and MEMBER. PROJECT_OWNER cannot be the target of a change, and you cannot change your own role from this screen. A confirmation dialog appears before the change is applied.
Admins can remove any non-Owner member. Admins cannot remove each other (same tier), and removing yourself is not allowed — use 'Leave' instead.
A 'Leave' button is shown only on your own row when you are not the Owner. After confirming in the dialog, you are sent back to the console. The last remaining Owner cannot leave until ownership is handed off.
For the full invitation lifecycle — email expiration, resending, etc. — see the Members & Invitations doc.
API Keys
Authentication keys Claude Code uses to talk to the AIFlare server. Keys are issued per project, and once dismissed nobody — not even the issuer — can read the key value again.
Owner, Admin, and Member all have the API_KEY_CREATE permission on a project, so any project member can use the 'Issue' button. Provide a name and confirm; a new key is created and the full value is shown exactly once in a banner at the top.
The banner shown right after issuing a key includes a 'Download aiflare.yml' button that saves a config file containing the key. Drop it at the root of your Claude Code project and it is picked up automatically.
Keys are listed with name, prefix, creation date, and status. With PROJECT_EDIT permission you see keys issued by every member; without it you only see your own keys.
Each row has a 'Revoke' button that deactivates the key immediately. You can only revoke keys you yourself issued — keys belonging to other members are not revokable from your side. Once revoked, every request using that key is rejected.
The full value of an issued key cannot be viewed again once you dismiss the banner. Save it via 'Download aiflare.yml' or copy it into a password manager. If you suspect a key has leaked, revoke it immediately and issue a fresh one.
Permission Matrix
A summary of what each project role can do from this settings screen. Owners can perform every action, Admins can do everything except deleting the project, and Members are mostly limited to read access and managing their own keys.
| Capability | Owner | Admin | Member |
|---|---|---|---|
| Open the settings screen (when a member of the project) | ✓ | ✓ | ✓ |
| Edit project name and description | ✓ | ✓ | – |
| Invite members by email | ✓ | ✓ | ✓* |
| Toggle 'Allow member invites' | ✓ | ✓ | – |
| Change another member's role | ✓ | ✓ | – |
| Remove non-Owner members | ✓ | ✓ | – |
| Issue a project API key | ✓ | ✓ | ✓ |
| Revoke an API key you issued | ✓ | ✓ | ✓ |
| View API keys issued by other members | ✓ | ✓ | – |
| Delete the project | ✓ | – | – |
✓* (conditional): Members can send email invitations only when an Admin has turned on the 'Allow member invites' toggle. Everything else for Member is static — API_KEY_CREATE is granted to Members by default, so any member can issue their own project API keys, and revoking is restricted to keys they themselves issued. 'Remove non-Owner members' is subject to the constraint that Admins cannot remove each other.