# One account for your whole team, with each person seeing only their work Keep every app in one Overskill account and share it with your team one app at a time or a whole project at once. Each person sees only what you share with them, and you choose who can edit and who can only view. - Share one app, or a whole project - Owner, Editor or Viewer - One account, one credit balance ## The problem it solves Inviting someone to an Overskill account has always given them every app in it. The collaborators list on an app was only a list: every member could still open, change and delete every app. So teams with several businesses or clients spread their work across separate accounts to keep it apart. Team sharing ends that. Keep all of your apps in one account, with one credit balance, and give each person just the apps and projects they work on. ## Two ways to share A project uses three roles: Owner, Editor and Viewer. A single app is shared as Editor or Viewer. Most teams use both. ### Share one app Open the app, click **Share**, then the **Team** tab, and add a teammate as an Editor or Viewer. If they have Project access, they see that one app and nothing else. Good for a freelancer on a single funnel, or a reviewer on one build. ![The Share window for an app called Online Store, with Editor and Viewer choices and a teammate listed under "Shared with just this app".](https://www.overskill.com/assets/features/team-sharing/share-one-app-ecb4f070391ff85f940275dbc6cac08f1079ea871a03c8918b04ecce2ba42764.jpg) ### Share a project Group your apps into a project, such as one for each business or client. In the sidebar, open the project's menu and click **Share**. Everyone you add gets that role on every app in it, including apps you add later. Each app's Share window shows them under the project they came from. ![A project's menu in the sidebar, with Share at the top.](https://www.overskill.com/assets/features/team-sharing/sidebar-share-63872d3270c8c7323b1dac7aacafc39c43bf83457267c19d90c411d1844a599d.jpg) ![The Share window for an app in the Coaching project, listing a teammate as "Editor · from project Coaching".](https://www.overskill.com/assets/features/team-sharing/from-project-8256bda623e83d8d64f9443b742e0fd8d4173ccb923ffad36b45b4f561cc0cb8.jpg) ## An example: one company, three businesses Say your account has three projects: **Coaching** (a webinar funnel, a member portal and a booking app), **Supplements** (an online store and a product quiz) and **Events** (a ticketing app). - **Sarah** is an Editor on the Coaching project. She builds and publishes those three apps and never sees the others. - **Marcus** is a Viewer on the Events project. He can open and preview the ticketing app, but can't change it. - **A freelance designer** is an Editor on just the online store. They see that one app and nothing else in Supplements. > **The higher role wins.** If someone has a role on a project and a different role on one of its apps, they get whichever is higher. ## Who can do what Each person has one level for the whole account, set by an admin on the **Members** page. People with Project access also get roles on the projects and apps shared with them. ![The Members page with an access choice for each person, an Access option when inviting, and a "New people join as" setting.](https://www.overskill.com/assets/features/team-sharing/members-191f3c58f597495354ea0fa8ecb9d63c801ea33fe8885a2f4afdeab7a48a21c8.jpg) ### Admin Sees and manages everything: every project, every person, billing and connected services. ### Full access Builds and edits every app in the account, the way team members always have. ### Project access Sees only the projects and apps shared with them. Here's what each role on a project or app allows: - **Owner:** everything, including deleting apps, moving them between projects, and adding or removing people already in the account. - **Editor:** build, edit and publish. Can't delete apps or change who has access. - **Viewer:** open and preview. Can't make changes. Secret settings like API keys are shown masked, never in full. Whoever builds an app becomes its Owner. ## Built for running a team ### See who has access, and why The Share window on an app or a project lists every person and where their access comes from, like "Admin · all apps", "Editor · from project Coaching" or "Viewer · shared directly". ### No surprises when you move an app Moving an app to a different project changes who can open it. Before anything moves, you see exactly who gains access and who loses it. ### A heads-up when someone's added People get an email and an in-app notice when they're added to a project. ### Monthly credit limits per person Admins can set a monthly credit limit for each person with Project access, and see spend broken down by person. Work that's already running when someone hits their limit finishes and is billed as usual. They can't start new work until an admin raises the limit or the month resets on the 1st. People with a limit run one build at a time. ### Shared connections are managed for the whole account Services like Gmail are connected for the whole account by an admin or someone with Full access. People with Project access can use what's already connected in their apps, but can't add, change or remove those connections. ### Clean offboarding Remove someone from the account and their access ends at once, and any API keys they made stop working on your apps. ## Getting started ### Turn on team sharing An account admin clicks **Turn on team sharing** on the Members page. Nobody gains or loses access to any app when you do. Very large accounts (more than 200 people or 500 apps) contact support and we switch it on for you. ### Group your apps into projects One project for each business, client or team works well. ### Set who sees what On the Members page, set people to Project access, or choose that new people join with it. Then share projects with each person as Owner, Editor or Viewer, or share a single app as Editor or Viewer. ### Optional: set credit limits Give anyone with Project access a monthly credit limit. ## Common questions ### Whose credits get used? The account's. Everyone draws from one shared balance. Per-person limits are an optional budget on top of that, and admins can see spend by person. ### Will anything change for people already on my account? No. Turning it on keeps everyone's current access exactly as it is, and we check that before it's saved. Then you choose who moves to Project access. To turn it back off, contact support. ### How is this different from the collaborators list I already have? Before, collaborators was just a list, and every member could still open and change every app. Now the roles you set are enforced everywhere: in the builder, the API and connected tools. ### Is this the same as the "Users" settings inside an app? No. Those settings are for your app's own customers and who can sign in to the app you built. Team sharing is for your team inside Overskill: who can open, build and publish your apps. ### Can I move apps from my other accounts into the shared one? Not directly yet. You can remix (copy) an app into the shared account if remixing is turned on for it. The copy starts as a new, unpublished app, so publish it again from the shared account. ### Can I share with someone outside my company? Yes. An admin types their email in the Share window, and they're invited to your account with Project access, so they see only what you shared. They become a member of your account. ## Bring your team into one account. Turn on team sharing from your account's Members page, then share your first project. --- Updated October 9, 2026. Page: https://www.overskill.com/features/team-sharing