Documentation Index
Fetch the complete documentation index at: https://archie.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
The team members surface in your organization controls who has access, what they can do, and how their AI credit usage is tracked.
How do I invite a new member?
Open Organization → Members and click Invite member. Provide an email and a role. The invitation email contains a one-click link — when the recipient clicks it, they sign in or sign up and join your org immediately.
You can resend or cancel pending invitations from the same surface.
Roles
Archie ships four roles, with custom roles available on Enterprise:
- Admin — full access. Manage members, billing, integrations, and all projects.
- Frontend Builder — build, edit, deploy frontend code. Cannot change billing, members, or integrations.
- Backend Builder — same scope as Frontend Builder, focused on backend modules.
- Viewer — read-only on assigned projects. Available on Pro plan as collaborator invites.
Roles are assigned at the organization level and can be overridden per-project on Team and Enterprise.
Per-project roles
In a Team or Enterprise plan, assign someone Backend Builder org-wide and Frontend Builder on a specific project where they need broader access. Open the project settings and adjust their role for that project only.
Per-member credit limits
On Team and Enterprise, you can cap how many AI credits each member can consume per cycle. Useful when you want to give a junior builder access without risking the pool. Open the member’s row and set a credit limit.
Pooled credit usage shows on the Plans and credits page with a per-member breakdown.
Removing a member
Click Remove on the member’s row. They lose access to all projects in the organization immediately. Their previous activity (commits, blueprint edits, comments) remains attributed to them in the activity feed.
If they were the last admin, designate another admin first — the system blocks removal of the only admin to prevent lockout.
Activity and audit
The org-level Activity feed shows what every member has been doing. Filter by user, project, or action type. Audit retention follows the plan: 90 days on Team, custom on Enterprise.
Outside collaborators
For one-off external collaborators (a contractor, a designer reviewing the prototype), invite them as Viewer instead of consuming a paid seat. Viewers do not count against your seat limit and have read-only access.
