Collaboration is essential for effective app store optimization. PressPlay makes it easy to add team members to your organization, granting them access to your publishers, apps, and experiments. This guide walks through the process of inviting users and ensuring they're set up for success.
Before you can add team members to your organization, ensure that:
You have appropriate permissions (admin or write access to organization management)
The organization is active (deactivated organizations cannot add new members)
You know the user's email address or user ID in the PressPlay system
Adding a team member to your organization is straightforward. The system handles most of the complexity behind the scenes, but understanding the process helps ensure smooth onboarding.
First, you need to identify who you want to add. This can be done in two ways:
Existing PressPlay users: If the person already has a PressPlay account, you can add them directly using their user ID or email address
New users: If they don't have an account yet, they'll need to create one first through the standard registration process
PressPlay's authentication system ensures that only verified users can be added to organizations, maintaining security and accountability.
Once you've identified the user, adding them is simple:
Navigate to your organization's user management section
Select the option to add a new team member
Enter the user's ID or search for them by email
Confirm the addition
The system will immediately grant the user access to the organization. They'll be able to see the organization in their organization list and switch to it from their dashboard.
After adding the user, assign them the appropriate role for their responsibilities. PressPlay supports different permission levels:
Read access: View experiments, reports, and configurations but cannot make changes
Write access: Create and modify experiments, generate assets, and manage day-to-day operations
Admin access: Full control including team management, publisher connections, and organization settings
Choose the role that gives the user the permissions they need without over-granting access. You can always adjust roles later as responsibilities change.
Understanding what happens behind the scenes helps you support new team members:
As soon as you add a user, they gain immediate access to the organization. No waiting period or approval process is required—they can start working right away.
The organization appears in the user's organization list. They can switch between all organizations they're a member of using the organization selector in the interface.
Based on their assigned role, the user can now access:
All publishers connected to the organization
All apps within those publishers
Experiments, assets, and reports across the organization
Organization settings and configurations (if they have appropriate permissions)
Adding a user doesn't change historical data or audit logs. Previous actions remain attributed to the users who performed them, maintaining a clear record of who did what and when.
Follow these guidelines to ensure smooth team onboarding:
Before adding a user, think about what role they should have. Consider their responsibilities, experience level, and need for access. Starting with appropriate permissions prevents security issues and reduces confusion.
Add team members when they need access, not far in advance. This reduces the window for unused credentials to potentially be compromised and ensures users remember their access when they actually need it.
Maintain a record of who has access to your organization and why. This helps during team transitions, troubleshooting, and periodic access reviews. Consider including:
User name and contact information
Role and permissions
Date added
Reason for access
Expected duration (for contractors or temporary team members)
After adding someone, let them know:
They've been granted access
What organization they've been added to
What their role and responsibilities are
Where to find relevant documentation and resources
Who to contact if they have questions
A brief onboarding message goes a long way in helping new team members feel welcome and get up to speed quickly.
When in doubt, start with read access. Users can explore the platform, understand existing experiments, and learn the system without risk of accidentally changing important configurations. Upgrade their permissions once they're comfortable and need additional capabilities.
When onboarding multiple people at once:
Add them individually: Take time to assign appropriate roles for each person
Group similar roles: Add all analysts together, then all experiment managers, etc.
Verify each addition: Check that each user appears in the team list with correct permissions
Conduct group onboarding: Consider a team orientation session to introduce the platform
If you encounter problems when adding team members:
If you can't find a user to add, they may not have created their PressPlay account yet. Have them complete the registration process first, then try adding them again.
If adding a user fails:
Verify you have permission to add users to the organization
Check that the organization is active (deactivated organizations can't add members)
Ensure the user isn't already a member of the organization
Confirm the user ID or email is correct
If a user reports they can't see the organization after being added:
Have them log out and back in to refresh their session
Verify they're looking in the correct organization selector
Check that the addition was successful in the team member list
Ensure they're logged into the correct account
When adding external collaborators like contractors or client stakeholders:
Use read-only access by default to protect sensitive data
Document the external relationship clearly
Set reminders to review their access periodically
Remove their access promptly when the collaboration ends
When someone joins to replace a departing team member:
Add the new person first
Allow overlap time for knowledge transfer if possible
Ensure the new person has appropriate access before removing the departing member
Document any unique responsibilities or knowledge the departing person held
Users can be members of multiple organizations simultaneously. This is normal and expected, especially for:
Agency team members managing multiple clients
Platform administrators
Consultants working with several teams
Each organization membership is independent—adding someone to one organization doesn't affect their access to others.
Once you've added team members:
Monitor their initial activity: Check that they're able to log in and access resources
Be available for questions: New users often need guidance during their first few days
Gather feedback: Ask about their onboarding experience to improve the process
Review permissions periodically: Ensure roles remain appropriate as people grow into their positions
Building a strong, well-managed team is foundational to successful app store optimization. By thoughtfully adding team members and setting them up for success, you create an environment where everyone can contribute effectively to improving your app's performance.
