Build together with role-based access
Work as a team on projects with shared access to every game and per-role permissions for who can view, edit and publish.
One studio, the whole team
Bring developers, reviewers and partners into the same game record with the right level of access for each.
Everyone on the same game record
Developers and reviewers work against one connected record — no scattered copies, no guessing which build is current.
Role-based control over view, edit and publish
Give each member exactly the access they need — view, edit or publish — with per-role permissions across projects.
Per-role access
Set view / edit / publish rights by role.
Across projects
Apply roles consistently to every game.
Collaboration at a glance
Team access
Bring the whole team into the studio.
Shared records
One connected record per game.
Roles
View, edit or publish per member.
Developers
Work on sources together.
Reviewers
Review against the real build.
Publishers
Control who can ship to RGS.
Collaboration questions
How teams work together and control access.
Yes — developers, reviewers and partners share one connected game record in the studio.
Per-role: you decide who can view, edit and publish, applied consistently across projects.
Everyone works against the same record, so there's no ambiguity about which build is current.
Bring your team into the build
Shared projects and role-based permissions, end to end.
