Permissions

Major provides granular access control at both the organization and application level.

​

Organization Roles

​

Application Permissions

Each app has its own permission levels:

• Admin: Full control including sharing and deletion.
• Edit: Can modify the app in the editor and create new versions.
• View: Can run and use the deployed application.

​

Sharing Access

You can share access to your application with specific:

• Individuals: Invite users by email.
• Groups: Grant access to entire teams at once.

​

Resource Permissions

Resource permissions control who can use connectors and at what level:

​

Sharing Access

You can share access to connectors with specific:

• Individuals: Invite users by email.
• Groups: Grant access to entire teams at once.

​

Inviting Members

Go to Settings > Members and click Invite Members to open the invitation dialog. You can:

• Paste multiple email addresses at once (comma or newline-separated)
• Select a role to assign to all invitees
• Send batch invitations

The dialog shows real-time progress for each email address (pending, sending, success, or failed) and displays a summary when complete. Email addresses are deduplicated automatically, and validation errors appear inline if needed.

​

Accepting an Invitation

When you receive an invitation and sign up as a new user, your account is automatically added to the organization with the role specified in the invitation. You’ll see a success confirmation and be redirected to your organization dashboard. No additional action is required to accept the invitation.

​

Per-User OAuth

Some connectors (like Google Calendar) support per-user OAuth, allowing end-users to authenticate with their own accounts instead of using shared credentials.

​

Authentication Modes

When configuring a resource, you choose between two modes:

• Shared — One shared OAuth account for all app users. The person deploying the app provides the credentials.
• Per-user — Each user authorizes their own account. Major redirects unauthenticated users to a /connect page to complete OAuth.

​

Connected Accounts

Users manage the per-user accounts they’ve authorized from the Connected Accounts settings page — viewing connected services, disconnecting them, and re-authenticating when credentials expire.

​

Groups

Groups allow you to manage permissions for sets of users efficiently.

• Inheritance: All members of a group inherit the permissions granted to the group.
• Default Permissions: Groups can be configured to have default permissions (e.g., View) on all new apps created in the organization.
• Group Settings: Access group details, manage members, view applications and connectors through the group settings page. The Members, Details, Applications, and Connectors tabs display all associated data for your group.

​

Creating Groups

The Create Group button in Settings > Groups is visible to all users. Admin users (those with canCreateApplications permission) can create groups. Non-admin users see the button disabled with a tooltip that says “Only organization admins can create groups.”

​

Managing Group Members

Organization admins can add both organization members and pending invitees to groups. When you add a pending invitee to a group, they automatically become a group member once they accept their organization invitation. The group members page displays all members with their status:

• Active members show their name and email
• Pending members (invitees not yet accepted) display a “Pending” badge

When inviting users to a group, the add-members dialog shows both current organization members and pending invitees, letting you pre-add invitees before they join.

​

All Users Group

Every organization includes a special All Users group containing every member of the organization.

• By default, this group is set to have View permissions on every new app, making internal tools open-by-default within the company.
• You can modify this setting if you prefer a more restrictive default.

​

All Builders Group

The All Builders managed group automatically syncs membership based on organization role — anyone with Builder role or higher is included.