About your organization and teams

Organizations are only supported for customers with a Google Workspace administrator and users with AppSheet Enterprise accounts. See AppSheet pricing.

Learn about organization and teams in the following sections:

What is an organization?
What is a team?
About the system-generated teams
Supported roles for an organization and teams

What is an organization?

An AppSheet organization provides organization administrators with a centralized tool to manage all of the teams in the organization and delegate team management responsibilities to team administrators.

For Google Workspace users with AppSheet Enterprise accounts, an AppSheet organization is created for you and is based on the Workspace organization. By default, the AppSheet organization is named after your primary domain, such as mycompany.com.

What is a team?

An AppSheet team is a group of AppSheet users who are members of a business unit. Teams provide team root and administrator accounts with centralized tools for managing governance, security, policies, analytics, and billing of team members to ensure that AppSheet is compliant with the business unit's requirements. Common assets like data sources and user domains can be defined once by the team root or administrator and used by all app creators in the team.

Team root privileges are automatically assigned to Google Workspace admins with:

AppSheet Enterprise accounts.
AppSheet service admin privileges (as defined by Workspace). Super Admins and Workspace Service Admins include these privileges, by default. See Prebuilt administrator roles.

About the system-generated teams

An AppSheet organization includes the following system-generated teams by default:

Workspace organization team that includes all Google authenticated users in your organization
Domain-based teams for all verified domains associated with your Workspace account allowing users to sign in with non-Google authentication methods

All users in a domain-based team will receive an email notification when the team is added to an AppSheet organization.

You aren't obligated to use the system-generated teams. You can create your own teams using a Google Group as long as each team has a root admin. See Add teams to an organization.

You can assign root admins using the Workspace Admin Console or AppSheet Admin Console, as described in the following sections:

Assign AppSheet admin privileges to Google Workspace admins
Assign team member roles on the Manage organization page

To determine the best option for your organization, consider the following:

System-generated team names can't be changed. Group-based team names are based on the name of the Google Group.
You can't move a user from one system-generated team to another system-generated team. A user can only be moved to another team if they are included in a Google Group-based team and authenticate through Google.
Any users that authenticate through non-Google authentication methods (such as Microsoft, Okta, and so on) will be automatically added to a domain-based team.
If there was no verified Workspace organization when a user first signed in to AppSheet, then they might be added to a domain-based team instead of the Workspace organization-based team.

Supported roles for an organization and teams

The following figure shows the hierarchical relationship between an organization, and its teams and members. As shown, there can be multiple organization admins, team admins, and team members; however, there can only be one team root account.

Organization hierarchy

Supported roles and permissions for an organization and its teams are summarized in the following table.

Role	How many?	Permissions
Organization administrator	One or many per organization	View all teams and team members in an organization Add a team to the organization that is based on an existing Google Group See the number of apps created by app creators on any team Update the team member roles for any team to delegate team administration Delete teams in an organization Define organization, team, and account governance policies
Team root	One or many per organization	Define, remove, and delete team members in your current team View team member account details, including number of apps View team app details and receive an emailed app summary report View and share resources with team members (sample apps, databases, data stores, and so on) View security for your team Monitor your team app activity, usage, and billing information, and download membership data Configure team settings including: Restrict who can create apps Restrict the recipient list for outgoing email Set the public app owner Set the AppSheet session length Define team and account governance policies, and view organization governance policies. Export team audit logs to Big Query Transfer apps and databases between team members Automate the removal of team user accounts
Team administrator	One or many per team	Define and remove team members in your current team View team member account details, including number of apps View team app details and receive an emailed app summary report View and share resources with team members (sample apps, databases, data stores, and so on) View security for your team Monitor your team app activity, usage, and billing information, and download membership data Configure team settings including: Restrict who can create apps Restrict the recipient list for outgoing email Set the public app owner Set the AppSheet session length Define team and account governance policies, and view organization governance policies. Export team audit logs to Big Query
Team member	One or many per team	Use AppSheet to create apps View team member account details View and share resources with team members View your organization and team governance policies Define governance policies for your account

Was this helpful?

How can we improve it?

About your organization and teams

What is an organization?

What is a team?

About the system-generated teams

Supported roles for an organization and teams

Was this helpful?

Need more help?

Try these next steps: