> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/team-and-account.md). # Team & account Manage your team, branding, sign-in security, billing and reports.


Team members and admins	Create your team, invite members, choose who is an admin, and deactivate or reactivate users.	Team members and admins
User groups	Split a large team into groups so each group shares requests, contacts and templates only among its own members.	User groups
Branding	Add your logo and colors to the emails and upload pages your recipients see.	Branding
Single sign-on (SSO)	Let your team log in to Pipefile through your company's identity provider, and optionally sync users and groups from your directory.	Single sign-on (SSO)
Two-factor authentication and device verification	Protect your login with an authenticator app or security key, keep backup codes, require two-factor for your team, and understand new-device emails.	Two-factor authentication and device verification
Change your email or password	Change your name, login email or password, or reset a forgotten password.	Change your email or password
Billing, plan changes and canceling	Upgrade, change plan or seat count, update your card, download invoices, and cancel your subscription.	Billing, plan changes and canceling
Reports	Download a CSV of every request you can see, with status, progress, recipients and tags in one row each.	Reports
Contacts	See, edit and import the people you send requests to.	Contacts

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.pipefile.com/team-and-account.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.