Organizations

Overview of the organization management tools in the Developer Portal.

An organization is the highest level in the Epic Online Services (EOS) product management ecosystem. It encompasses a team of people and all the products associated with that team, such as a publisher or game studio.

All members of your organization are considered team members in the Developer Portal.

For example:

  • Organization - Epic Games

    • Product - Jazz Jackrabbit

    • Sandbox - Development

      • Deployment - DevGame01

    • Sandbox - Staging

      • Deployment - QATestGame01

      • Deployment - AlphaGame

      • Deployment - BetaGame

    • Sandbox - Live

      • Deployment - LiveGame

When you create an account on the Developer Portal and are not a member of an existing organization, a new organization is created. For existing organizations, organization Admins can add or remove team members and manage their roles through the Developer Portal.

Once created, Admins can also configure your organization's entity type from the Settings tab in the Developer Portal under Organization. Your entity type can either be a company or an individual:

  • Company - Available for incorporated entities and indicates that your organization represents a legal entity.

  • Individual - The default entity type for an organization and indicates that all of the members of the team are acting on their personal behalf.

There is no functional difference in the features and services available to you as an organization. You may only encounter slightly different workflows in the services tailored to your organization type.

The Organization page of the Developer Portal is where you manage your team members, their roles, view licenses, and configure your console developer access.

If you are a member of more than one organization, a prompt will ask which organization you want to access at sign-in. After sign-in, you can always select a different organization from the dropdown by your current organization's name in the top banner.

Team Member Management

Team members within your organization appear as a list on the Team tab of your Organization page in the Developer Portal. Each team member is granted a role within the organization that gives them permissions to different tools in the Developer Portal.

To add a new member to your organization, click Invite on the Team tab. A prompt requests the email address for the new member, their role, and for which products. After pressing Invite, the new member is added to your organization once they accept the invitation.

Once a team member is part of your organization, an Admin can remove or change the access rights of a member by clicking on More Options for that member.

Roles

Each team member has a role granting them permissions for different tools in the Developer Portal. You can create additional roles, but the default roles are as follows:

Role

Description

Access

Admin

Has access to all functionality on the Developer Portal

All available tools

Game Services

Has access to Game Services tools

Product Management, Matchmaking, Leaderboards, Stats, Achievements, Player Data Storage, Lobbies

Community Tools

Has access to player management and moderation tools

Ticketing System, Metrics, Account Linking

Finance

Has access to finance data of the publishing organization

Reports, Payout

Store

Has access to Store publishing tools

Builds, Reports, Analytics, Product Pages, Mods

Epic Account

Has access to the Epic Account

Epic Account

Adding Roles

Admins can create new roles for their organization by clicking New Role from the Roles tab. A modal slides open for you to name, describe, and choose access for the new role. Once satisfied with your selections, click Create to add it as another role option for your organization.

Licenses

The Licenses tab organizes your active licenses and agreements for your organization and allows you to review them as needed.

Player Groups

Player Groups allow you to manage external users' access to private sandboxes and deployments. By default, private sandbox or deployment access is denied to external users unless they are given permission by using Player Groups. For example, you can add your QA team's account ID to a group so they can test on their own private version of your product.

Access to a private sandbox or deployment is automatically granted to organization users that have access to the associated product.

You can view and manage external user access to private sandboxes and deployments within the Developer Portal by selecting the Player Groups tab on the Organization dashboard.

Creating a New Player Group

To create a new Player Group, click Create New Group. Each group you create requires the list of external account IDs you want to grant access. These account IDs can belong to any supported identity provider.

You can also import your list of account IDs with a .CSV file. This can be more efficient if you have many IDs from multiple providers.

To streamline importing multiple IDs, you can download a template with the correct file format from the Import list tab. Here is a sample import list of player IDs using the above product management ecosystem example:

"identityProviderId","accountId","environment" "apple","ozortmlokh12kylmlftv70i2vo4i95pn","development" "epicgames","1gyi3tqjydprs03qmpj624wrhfxn2oa9","" "steam","nt7qtch0zvcol1wux1n5fkak57ubopa1","devgame01" "steam","ozortmlokh5039fjmlftv70i2vo4i95pn","development" "xbl","c3a6tjydprs03qmpj624wrhfxn2oa9","devgame01" "psn","75fgj3zvcol1wux1n5fkak57ubopa1","alphagame" "google","ozomodo7wh12kylmlftv70i2vo4i95pn","betagame" "apple","29xkdm3jydprs03qmpj624wrhfxn2oa9","betagame" "discord","nt7qtch0zvcol1wux1n5fkak57popo254",""

Once you finish assigning player groups to the appropriate IDs, select the sandboxes and deployments this group can access. Once you create the group, all external users in that Player Group can access the select private sandboxes and deployments.

You can always edit a Player Group from the Player Groups tab by selecting the More Options.

Console Developer Access

To gain access to console-related content, such as the EOS Console SDKs and specific documentation, you must configure your organization with your developer account for each console (Nintendo Switch, Playstation, Xbox, etc).

To manage your configuration and access settings, in the Organization page, on the Settings tab select Configure. After you confirm the status for your platform, go to the Console Developer Request for Epic Online Services to complete your request.