Team and permissions

The roles in the console, folder-level permissions for outside teams and freelancers, the records PVersion keeps, and removing someone from the team.

PVersion has two kinds of permissions. A role decides what a person can do in the console: create projects, send invitations, buy a plan and so on. An area permission decides which folders of a project a person can see and change. In most studios everyone works on the whole project; area permissions are for outside teams and freelancers.

Roles

Every member has a role in the studio: Developer, Admin or Owner. The person who opened the account is an owner; the person sending an invitation chooses the invitee's role.

Changing a role

Owners pick the new role from the Role list on a member's row on the Team page; the change applies immediately. You cannot change your own role there. The studio's only owner cannot be given a lower role; make someone else an Owner first.

Outside teams and freelancers

Outside teams and freelancers see only the part you open to them. You do this with areas: an area is a folder inside the project (for example Content/Characters), and each person gets a permission per area. These settings require the Admin or Owner role.

1. Defining areas

1. On the project page, go to the area settings from the server card on the right: Areas and permissions for projects on the main server, or Users, backups, license for the server's own project.
2. Open the Areas tab.
3. With Add area, give each area a Name and a Folder (relative to project root), for example Characters → Content/Characters. For Unreal and Unity projects, Unreal template and Unity template bring a ready-made list (levels, characters, audio, UI, code and so on).
4. Click Save.

While no areas are defined, everyone works on the whole project. Files outside the areas (for example the Unreal project file and Config/) are open to everyone, so a restricted person can still open the project. On a newly added area, everyone starts with write permission; restricting it is up to you.

2. Setting a person's permissions

1. On the same page, open the Users tab (for projects on the main server the tab is called User permissions).
2. Click the shield icon (Permissions) on the person's row.
3. For each area, choose Write, Read or None (see the table below).
4. Click Apply.

Write to all and Read for all set every area at once. The server enforces the permission on every request, and the person's workspace covers only the areas they are allowed. If you set permissions before the person sets up the project, files they don't need are never downloaded.

Who did what

PVersion keeps two separate records:

• File history: every submit to the project is recorded with the submitter's name, the time and the description. You see it in the Recent changes section on the project page and on the app's History page (History and undo).
• Activity log: the actions taken in the console; who did what, and when. Creating projects, sending invitations, changing roles, editing areas and permissions, taking backups, starting payments and so on. Admins see the last 100 entries at the bottom of the Team page. If the PVersion team takes an action in your console while helping you, that row is marked as such.

Removing someone from the team

An owner removes a freelancer whose job is done, or a team member who is leaving: click the bin icon (Remove from organization) on the person's row on the Team page and confirm with Remove.

• The person no longer sees the studio's projects in the console.
• Their account on the studio's servers is deleted too: they can't connect, and they no longer count as a user in your plan. Files they had open are released.
• Files on their computer are not deleted. Everything they submitted stays in the history under their name.
• Their PVersion account (console sign-in) is not deleted, so they can keep working with other studios.

If a server account can't be deleted, the console tells you. Then delete it yourself with the Delete icon on their row in the server's Users tab.