> For the complete documentation index, see [llms.txt](https://docs.rayon.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rayon.design/documentation/team-management-and-billing/teams.md). # Teams Rayon is great for **designers** that love to **collaborate**. To that end, **Rayon** offers **teams**: a simple way to share [**workspaces**](/documentation/team-management-and-billing/workspaces.md), **models**, **templates** and **libraries** while making sure everyone has appropriate access. ### Team setup and access Setting up a team can be done **at signup**, or later on, **in the project manager context menu**. In either case, Rayon will ask you to set a name for your team and to invite other users.

The **curation of users** having access to the team , as well as their **role**, and the **billing** attached to your team can be managed from the team's settings page.

### User roles When inviting users to an team, it is important to understand their role. \ Members can have **4 types of roles** in an team...

Role	View models	Edit models	Set team settings	Curate team users
Owner	true	true	true	true
Admin	true	true	true	false
Editor	true	true	false	false
Viewer	true	false	false	false

### Billing Billing in Rayon always happens at the organization level. \ At any time, the team's **owner** may... * Update their **team's plan (**[Learn more about Rayon's pricing](https://www.rayon.design/pricing)) * Update the **billing address** * Download **invoices** *** ### We are always available Book a demo with our team, [right here](https://b1kzip68v9f.typeform.com/to/Hgr0eQ4k#source=docs).\ To get some support, reach out to us through our **in-app support chat**. \ More about [our support policy right here](/other-resources/others/support-policy.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.rayon.design/documentation/team-management-and-billing/teams.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.