> ## Documentation Index > Fetch the complete documentation index at: https://docs.sellauth.com/llms.txt > Use this file to discover all available pages before exploring further. # Teams and Permissions > Give other people access to your shop with scoped permissions, instead of sharing your login. Team members get their own SellAuth account and their own access to your shop, which means their actions are attributable and their access can be revoked without changing your password. Managed under [**Team**](https://dash.sellauth.com/team) in the dashboard. ## Roles | Role | Access | | - | - | | **Owner** | Full control of the shop, including billing and team management | | **Member** | Whatever permissions you grant | A shop has one owner. Ownership can be transferred, and the transfer is permanent, so it is a handover of the shop rather than a way to share access. See [transferring ownership](#transferring-ownership). ## Inviting someone Invite by email address. They receive an email and an invite in their SellAuth dashboard under **Account > Invites**, and gain access once they accept. If they do not have a SellAuth account, they create one first, then accept. Free shops cannot invite team members. Business lets you invite up to 2 team members and Scale up to 10, in both cases not counting you. Members already on a shop stay if the plan drops, you just cannot invite more until you upgrade. ## Transferring ownership Ownership can only be handed to somebody who is already a member of the shop, so it is a three step process rather than a single action. Invite the person by email as you would any team member. The permissions you grant do not matter here, since they are about to receive everything. They have to accept the invite from **Account > Invites** before anything else is possible. Until they do, they are a pending invite rather than a member, and cannot be made owner. Once they appear as a member, use **Transfer Ownership** on their row. You will be asked for your password and your two-factor code, or an emailed code if two-factor is off. Transferring ownership **resets the shop's theme**, because themes are tied to the owner's account. The new owner has to import and apply a theme again, so plan the handover for a quiet moment rather than mid-sale. The transfer cannot be undone. The new owner controls the shop, including billing, and can remove your access. ## Permissions Permissions are granted per member and are grouped by area: orders, products, payment methods, customers, blacklist, and so on. Each one covers a specific action, such as reading orders, processing them, or creating blacklist entries. Grant what the role needs and nothing else. A support person handling tickets needs to read orders, process them and resend emails; they do not need to edit payment methods or change prices. Two permissions deserve particular care: * **Payment method access** exposes your processor credentials, which is effectively access to your money. * **Crypto payout permissions** are granted per coin. Anyone holding one can withdraw that coin to any address. See [Crypto Wallets](/guides/crypto-wallets#withdrawing-manually). Members without a permission see the relevant action greyed out rather than hidden, so they can tell it exists and ask you for it. **Themes belong to a user account, not to the shop.** Giving a member theme permissions lets them edit the theme the shop is currently running. It does not let them import, apply, rename, update, clone or delete themes, because those actions stay with whoever owns the theme, and that ownership cannot be reassigned. In practice a team member can work on your live theme, and only the owner can change which theme is live. This is also why [transferring ownership](#transferring-ownership) resets the theme. ## Reviewing what your team did **Activity Logs** record actions taken on the shop as created, updated, deleted or restored, with the affected record and a view of what changed. Use it when you need to know who altered a price, a product, or a payment method. ## Removing access Remove a member from the Team page. Access ends immediately. Do this the same day someone stops working with you. A dormant account with order and payment access carries the same risk as an active one, and nothing draws attention to it until it is used. ## Next steps Two-factor authentication and device sessions. The per-coin payout permission. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.