> For the complete documentation index, see [llms.txt](https://docs.luganodes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luganodes.com/rpc/platform-guide/teams-members-and-roles.md).

# Teams, members and roles

Bring your team in and control what each member can see and do

Everything on the platform belongs to an organization: apps, usage, billing and members. You can belong to several organizations with a different role in each, and switch between them from the bottom of the sidebar. Members require Growth or above; the Free plan is single user.

### Roles

Every member has one role per organization, set when they are invited and changeable later.

<table><thead><tr><th width="101.7578125">Role</th><th>What they can do</th></tr></thead><tbody><tr><td>Owner</td><td>Everything, including plan changes. One per organization, cannot be removed</td></tr><tr><td>Admin</td><td>Manage apps, keys, teams, members and alerts. Cannot change the plan</td></tr><tr><td>Billing</td><td>View usage and billing, upgrade the plan and update payment. Never sees endpoint URLs or API keys</td></tr><tr><td>Viewer</td><td>Read only access to apps, endpoints and statistics, limited by team access</td></tr></tbody></table>

### Inviting members

From Organization Settings, open the Members tab and select **Invite Member**, entering a name, email and role. The invitee gets an email link that is valid for 7 days; until they accept, they appear under Pending invites, where you can resend or cancel. If they don't have a Luganodes RPC account yet, they create one when accepting.

### Teams

Teams group members and control which apps Viewers can see. Owners and Admins create teams from the Teams tab and assign members to one or more of them.

* Every app is visible to all teams by default. Restricting an app for a team hides it from that team's Viewers, including in statistics.
* Access is additive: a Viewer in several teams sees an app if any of their teams has access. A member with no team sees all apps.
* Owner, Admin and Billing always see all apps regardless of team restrictions.

{% hint style="info" %}
Because the API key is embedded in the endpoint URL, any role that can view endpoints (Owner, Admin, Viewer) can use them. Only the Billing role is excluded from keys and endpoints.
{% endhint %}
