> 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/team-members-and-admins.md). # Team members and admins Create your team, invite members, choose who is an admin, and deactivate or reactivate users. Everything about your team lives on one page, **Team Settings** (`Settings` → **Team**). It has sections for **General**, **Users**, **Groups**, **SSO** and **Branding**. Only team admins can open this page; a member who isn't an admin is sent back to the dashboard. ## Create your team If you haven't set up a team yet, the **General** section asks for a team name. Enter it and click **Save**. The **Users** and **Branding** sections appear once the team exists. ## Invite members {% stepper %} {% step %} ### Open Users Go to [Team → Users](https://pipefile.com/dashboard/settings/team#users) and click **Invite members**. {% endstep %} {% step %} ### Enter email addresses Type one or more addresses in **Enter email addresses**. If your plan includes user groups, you can also pick groups under **Assign to Groups (Optional)**. {% endstep %} {% step %} ### Send Click **Send Invites**. Each person gets an email with a link to join your team. {% endstep %} {% endstepper %} Pending invitations are listed on the **Invitations** tab ([open it directly](https://pipefile.com/dashboard/settings/team?users=invitations#users)). Use the reminder icon to send an invitation again, or the delete icon to revoke it. An invitation expires after 30 days; sending a reminder extends it. {% hint style="warning" %} A person can belong to only one Pipefile team. If someone already created a Pipefile account with that email address, the invitation email isn't sent. Email and we'll help move them onto your team. {% endhint %} ## Admins and members | | Admin | Member | | ------------------------------------------------------------ | ----------- | -------------------------------- | | Send and manage their own requests and templates | Yes | Yes | | See every request and contact on the team | Yes, always | Only when **Shared inbox** is on | | Open Team Settings (invite, remove, roles, groups, branding) | Yes | No | | Upgrade or change the plan | Yes | No | The person who created the team is marked **Owner**. The owner can't be removed or reactivated by an admin, and admins can't reset the owner's two-factor authentication. To change someone's role, open the **...** menu next to their name and choose **Assign admin role** or **Remove admin role**. ## Manage a user The **...** menu next to each active user offers: * **Update user**: change their name or login email. A new email has to be confirmed by the user before it becomes their login. * **Reset two-factor authentication**: removes their authenticator app, security keys and backup codes so they can set it up again. See [Two-factor authentication](/team-and-account/two-factor-and-device-verification.md). * **Transfer requests**: moves all of this user's requests to another team member you pick. * **Remove user**: deactivates the user. They can no longer log in, but their requests and history stay with the team. Deactivated users are on the **Inactive** tab ([open it directly](https://pipefile.com/dashboard/settings/team?users=inactive#users)). From there you can **Reactivate user** or **Transfer requests** to someone still on the team. {% hint style="info" %} Before removing someone who has requests in progress, transfer their requests so a teammate gets the notifications and can follow up. {% endhint %} ## Team-wide settings In [Team → General](https://pipefile.com/dashboard/settings/team#general), click **Edit** to change: * **Team name**. * **Team alias**: a name recipients see as the sender of your team's request emails, instead of each member's own name. * **Shared inbox**: when on, members see each other's requests and contacts. When off, members see only their own requests and the ones assigned to them. Admins always see everything. * **Require two-factor authentication**: see [Two-factor authentication](/team-and-account/two-factor-and-device-verification.md). To have replies to request emails go to one shared address (for example ) instead of each sender's own email, contact . ## How members affect your bill Paid plans are billed per user. The invite window shows how many unused licenses you have. When an invited user accepts and you have no unused license, a seat is added to your subscription, prorated for the rest of the billing period. When you remove a user, the seat count goes down and the unused time is credited to your account. Reactivating a user adds the seat back. ## Related * [User groups](/team-and-account/user-groups.md) * [Assign requests to teammates](/requests/assign-requests.md) * [Billing, plan changes and canceling](/team-and-account/billing-and-canceling.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 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/team-members-and-admins.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.