Teams

What teams control

A team is the top-level container for MapToPlay. Every workspace, project, processing task, asset, export, saved provider credential, and billing limit is scoped to a team. Before you create or open a project, check the active team in the sidebar selector or old header.

When your account is created, the platform creates an initial team and makes you the owner. You can create additional teams from the Teams page, but Basic-team activation is limited: after your active Basic team is used, additional Basic teams may be created as inactive draft teams until you upgrade or free capacity.

Open and select a team

Expand the team and workspace control in the sidebar and select Manage to open Teams & workspaces. The first tab shows your teams. Search by name, role, tier, or description, use Sort to order names, and use Filters for active or inactive teams. Select a team to see its profile, workspaces, and members together.

Selecting a team on this page shows its settings without changing the active team used by the rest of the app. Choose the active team and workspace in the sidebar or old header before returning to projects.

• Use the Active only and Inactive only filters when a team appears to be missing.
• Use search when you belong to many teams; it matches team name, your role, tier, and description.
• The team list shows how many teams match the current search and filter.

Create a team

Click New team in the Teams & workspaces title row. Enter a team name and submit the dialog. The new team is created with you as owner. Team creation only asks for a name; description, avatar, members, credentials, and other details are configured after creation.

If you already own the maximum number of active Basic teams, the new team is created as an inactive draft when draft capacity is available. If the inactive draft limit is reached, MapToPlay asks you to delete an unused draft team first.

• Team name is required.
• The default user-facing tier is Basic.
• The creator is added as owner immediately.

Invite an existing user

Select the team and use the Team members form. Enter the exact username or email address of an existing MapToPlay account, choose the starting role, and click Send invite. MapToPlay does not autocomplete accounts and does not send an invitation email. The username or email is used only to find that existing account.

If no account matches, the form reports that the user does not exist. If the account is already a member or already has a pending invitation to this team, the invitation is rejected with a clear duplicate message.

Sending the invitation creates a pending seat. That seat immediately counts toward the team member limit, so it cannot be promised to another person while the invitation is waiting. An owner or admin can cancel the pending invitation to release the seat.

• There is no user search or autocomplete: enter the full username or email yourself.
• No email is sent. The invitation is delivered inside MapToPlay.
• Pending invitations appear on the Teams tab with their reserved role and a Cancel button.
• Owner is not an invitation role. Invite the person first, then transfer ownership after they accept.

Accept or reject an invitation

The invited person receives a bell notification that names the inviter, the team, and the proposed role. Accept and Reject buttons are available directly in the notification. The same pending invitation is also shown at the top of the Teams tab, so clearing a notification does not leave the invitation impossible to find.

Accepting converts the reserved seat into an active membership and makes the team available in the team picker. Rejecting removes the pending seat. In both cases, the inviter receives a bell notification with the result.

• Accept: join the team with the role selected by the inviter.
• Reject: decline the invitation and release its reserved seat.
• Cancel: the owner or admin withdraws a still-pending invitation and releases the seat.
• A used, rejected, or cancelled invitation cannot be accepted later; a new invitation must be sent.

Roles and real permissions

A role controls both the buttons a member sees and the changes MapToPlay accepts from that account. Choose the lowest role that gives the person the work they actually need.

• Owner — complete control. Can manage members and team settings, create/edit/delete projects, edit in the Editor, run or retry processing, launch exports, transfer ownership, and apply or revoke that owner’s Patreon subscription benefits.
• Admin — operational team control. Can manage members and team settings and can do all project, Editor, processing, and export work. Cannot transfer or alter ownership and cannot apply, move, or revoke Patreon subscription benefits.
• Creator — creates and delivers projects. Can create, edit, archive, and delete projects; has full Editor access; can launch or retry processing tasks and launch exports. Cannot invite, remove, or change team members and cannot manage ownership or subscriptions.
• Editor — edits project content only. Can open existing projects and add, edit, or remove features in the Editor. Cannot create, archive, or delete projects; cannot launch or retry processing; cannot launch exports; and cannot manage team members.
• Viewer — read-only. Can open project pages and inspect the Editor, but editing controls are unavailable. Cannot create projects, edit features, run tasks, launch exports, or manage members.

Change roles and transfer ownership

Owners and admins can change a member between Admin, Creator, Editor, and Viewer. Only the current owner can assign Owner to another active member. That action transfers ownership and changes the previous owner to Admin.

The current owner cannot simply be removed or demoted. Transfer ownership first, confirm that the new owner is correct, and then let the new owner change or remove the former owner if needed. If a removed member has a profile image charged to this team, that image moves to another team they belong to; if they have no other team, it is removed.

Rename, avatar, and deletion

In the selected team panel, owners and admins can rename the team, upload an avatar, remove the avatar, or delete the team. Avatar uploads accept PNG, JPEG, and WebP images; the image is cropped before upload and must pass the managed image size limit.

Deleting a team is destructive. The confirmation dialog requires the word DELETE, then permanently removes the team, its workspaces, projects, project assets, uploaded source files, and team/workspace avatars. A member's profile image moves to another team they belong to; if they have no other team, that image is removed.

• A team cannot be deleted while any project in the team has a running task.
• Deleting a team also deletes every workspace and project inside it.
• Only owners and admins can rename, delete, upload avatars, remove avatars, add members, change roles, or remove members.

Provider credentials

Open the Credentials tab in Teams & workspaces and choose a team in the title row to view its provider credentials. Search filters the visible credential cards. Owners and admins can use Add credential in that row, then edit or remove saved cards. Credentials are stored at team scope so project creation and reprocessing can reuse them when a data provider requires a token or username/password.

When choosing provider source data, DTM providers with credential requirements can use a saved team credential instead of entering credentials manually. This is why provider credentials live on the team, not inside a single project.