# Team seats and shared site access Invite colleagues into the account so publishing is not one person's login. Access can be scoped, so a contractor sees the sites they work on and nothing else. ## Plan availability Seats start on Business, which includes 5. The largest plan includes 25. - **Free:** single user - **Starter:** single user - **Pro:** single user - **Business:** 5 seats - **Enterprise:** 25 seats ## Publishing stops being one person's password Each colleague gets their own sign-in, their own audit trail, and access that can be narrowed to a subset of the sites. A shared login is the default arrangement in small teams and it fails in the same three ways every time: nobody can tell who published the broken version, the person who leaves still has the password, and the one account holder becomes a bottleneck the week they are away. Seats fix all three by giving each person their own access. Removing somebody is one action rather than a password change that has to be redistributed to everybody else. Access can also be narrowed. Sites are organised into spaces, and a teammate can be granted specific spaces rather than the whole account, which is how you give a contractor the two client sites they are working on without handing over the rest of your portfolio. Grant nothing and they see everything, so scoping is something you switch on deliberately; the dashboard is explicit about which of the two a person currently has. For agencies this pairs with custom domains per client and the freelancer workflow. ## How to use it 1. **Move to a plan with seats.** Seats start on Business, which includes 5. The plan sets how many people can be in the account at once. 2. **Invite by email.** They accept, set up their own sign-in, and appear in the account with their own name against their actions. 3. **Scope them if you need to.** Grant specific spaces to limit what a teammate can reach. Leave it open and they can work across the whole account. ## When people reach for this - **An agency with a contractor on two projects.** Scope them to those two client spaces. When the engagement ends, remove the seat, and nothing else about the account has to change. - **A marketing team that publishes without waiting.** Three people who each need to put a landing page up should not be queueing behind one login. Everyone publishes under their own name. - **A studio handing a project over.** Work stays in the account rather than in one designer's personal login, which is what makes a handover possible at all. ## Doing this without us The alternative is one shared password, which works right up until the moment it matters. - **Who published this version.** Droply: Recorded against the person who did it. A shared login: Unknowable. - **Someone leaves.** Droply: Remove their seat. A shared login: Change the password, tell everyone else the new one. - **Limiting what a contractor sees.** Droply: Grant them specific spaces. A shared login: Not possible; one login sees everything. - **Two people working at once.** Droply: Normal. Each has their own session. A shared login: Workable, but nobody can tell the sessions apart. - **Second factor per person.** Droply: Each account arms its own. A shared login: One shared secret, or none. Compared against sharing a single account, which is the arrangement most small teams start with. Checked September 2026. ## When this is not the right tool Seats are for people who work on the sites. They are not a way to give visitors accounts. - This is not visitor authentication. To restrict who can open a published page, use password protection instead. - Seat counts are set by the plan, so a bigger team needs a bigger plan rather than a per-seat add-on. - Permissions are per space rather than per action. There is no read-only reviewer role. - Billing stays with the account owner. Teammates cannot change the plan or the payment method. ## Frequently asked questions ### Which plan includes team seats? They start on Business, which includes 5. The largest plan includes 25. Plans below that are single-user accounts. ### Can I limit what a teammate can see? Yes. Grant them specific spaces and they reach only the sites in those spaces. A teammate with no grants at all has access to everything, so scoping is a deliberate step rather than a default. ### What happens when someone leaves? Remove their seat. Their access ends immediately and the sites stay in the account, which is the main reason not to run a team on one shared password. ### Do teammates need their own subscription? No. Seats are part of the account's plan. Each person signs in as themselves, and billing stays with the owner. ### Can two people publish at the same time? Yes. Each seat is a normal sign-in with its own session, and publishes are recorded against whoever made them. ### Can a teammate change the plan? No. Billing and plan changes stay with the account owner, so a seat cannot upgrade, downgrade or cancel the subscription. ## Related features - [Custom domains](https://droply.host/features/custom-domains) - [Public API](https://droply.host/features/api) - [Password protection](https://droply.host/features/password-protection)