Users & Access

Manage who has access to your Pckgr account and what they can do.

Account Owners manage access; Admins invite in their tenants; Read Only can view

In short

  • Pckgr has five roles: Account Owner, Admin, MSP Technician, Read Only and MSP Read Only.
  • Account Owners and MSP Read Only users have every tenant. Admin and Read Only get specific tenants; MSP Technicians get specific tenants or all of them.
  • A user with custom access can hold a different role in each tenant.
  • Only Account Owners can change a user's access or remove a user.

User roles

Account Owner
Full access to all tenants. Can manage users, tenants, billing, and all settings.
Admin
Can manage devices, apps, groups, deployments, policies, scripts, and the tenant’s settings and users within assigned tenants.
MSP Technician
The day-to-day work: devices, apps, groups, deployments, policies, scripts, Remote Desktop, Chat, and agent setup, plus Remote Shell and the Remote File Manager when the Account Owner allows it. Does not see Settings, Users, or Tenants, and cannot roll an app back. Granted per tenant, or on every tenant of the account including tenants added later.
Read Only
View-only access to assigned tenants, including a read-only view of Settings and Users. Cannot create, edit, or delete anything.
MSP Read Only
View-only access to every tenant of the account, including tenants added later: devices, apps, groups, deployments, policies, scripts, Windows Update, agent setup, the audit log and templates. Does not see Settings, Users, or Tenants, cannot start Remote Desktop or Remote Shell, and cannot create, edit, or delete anything.

Account Owners automatically have access to all tenants. Admin and Read Only users are granted access to specific tenants. MSP Technicians are granted either specific tenants or all tenants, now and in future. MSP Read Only is always granted on all tenants, now and in future.

Who can do what

Account OwnerAdminMSP TechnicianRead OnlyMSP Read Only
Devices, apps, groups, scripts, policies, deployments, Windows UpdateManageManageManageViewView
Remote Desktop (remote control of a device’s screen)YesYesYesNoNo
Remote Shell (a command prompt on a device)YesYesOnly when the Account Owner allows it in SettingsNoNo
Replay Remote Shell recordingsYesNoNoNoNo
Remote File Manager (files on a device)YesYesOnly when the Account Owner allows it in SettingsNoNo
Chat (typing with the person at a Windows device)YesYesYesNoNo
Agent setup, audit logYesYesYesView onlyView only
TemplatesYesNoOnly an MSP Technician on all tenantsNoView only
Roll an app back to an earlier versionYesYesNoNoNo
Settings page (tenant settings, self-service branding)ChangeChangeHiddenViewHidden
API keys for the public APIYesNoNoNoNo
Users page: see users and invitesYesYesHiddenViewHidden
Invite usersAny access typeAdmin, MSP Technician or Read Only, in tenants they administerNoNoNo
Change a user’s access, remove a userYesNoNoNoNo
Rename a tenantYesYesNoNoNo
Create or delete tenants, billing, delete the accountYesNoNoNoNo
Which tenantsEvery tenant, including new onesThe tenants they are givenThe tenants they are given, or every tenant including new onesThe tenants they are givenEvery tenant, including new ones

Templates span tenants, so they are open only to the Account Owner, to MSP Technicians on all tenants, and (to view) to MSP Read Only users. A user given access tenant by tenant does not see them, whatever their role.

Where a role has no access, the portal hides the control or the page. MSP Technicians and MSP Read Only users who open Settings, Users or Tenants by URL see a short "not part of your role" message instead of the page.

Someone who holds different roles on different tenants sees, on the Users page, only the users and invites of tenants where their role can open Settings (Admin or Read Only). Tenants where they are an MSP Technician are left out.

View users

Go to Settings > Users in the sidebar. The users table shows:

Email
The user’s email address.
Name
Display name.
Access
Role badges showing which tenants the user can access and at what level.
Last login
When the user last signed in.

Invite a user

  1. Click Invite user.

  2. Enter the person's email address.

  3. Pick an access type.

    Each card says what it grants:

    Account OwnerShown to Account Owners only
    Full access to every tenant, billing, users and settings.
    MSP Technician on all tenantsShown to Account Owners only
    Day-to-day work in every tenant, including tenants added later, without Settings, Users or Tenants.
    MSP Read Only on all tenantsShown to Account Owners only
    View devices, apps, groups, scripts, policies and deployments in every tenant, including tenants added later, without changing anything and without Settings, Users or Tenants.
    Custom per-tenant access
    Tick the tenants the person should have, then choose a role for each: Admin, MSP Technician or Read Only. An Admin can offer only the tenants they administer.
  4. Click Send invite.

    The person receives an email with a link to accept the invitation. On the page it opens they set a password, or click Accept with Microsoft and sign in with the Microsoft account for the invited address. The invite expires after 7 days.

The confirmation also offers Copy link, so you can send the invite link yourself if the email doesn't arrive.

Manage invites

The Invites section on the Users page lists pending and historical invites, and opens by itself while any are pending. Each invite shows the email, status, expiration date, and assigned access.

To cancel a pending invite, click Revoke. Revoking takes the same access as sending: only an Account Owner can revoke an Account Owner or all-tenants invite, and an Admin can revoke an invite only when they administer every tenant it includes. Users whose account has been disabled show a Disabled badge in the user list.

Edit a user's access

Only Account Owners can change a user's access; the edit and remove icons appear on the Users page for them alone.

  1. Click the edit (pencil) icon on a user's row.

  2. Pick an access type: Account Owner, MSP Technician on all tenants, MSP Read Only on all tenants, or Custom per-tenant access.

  3. For custom access, tick or untick tenants and set the role for each.

    At least one tenant must stay ticked.
  4. Click Save.

Moving someone from all-tenants access to custom access limits them to the tenants you tick. Moving them the other way gives them every tenant, including ones you add later.

Remove a user

Click the delete (trash) icon on a user's row and confirm. This removes the user from your account and revokes all their tenant access.

Removing a user, or lowering or removing their access, ends any remote desktop, remote shell or file manager session they have open where they no longer have access. Their audit history and shell recordings stay; the recordings still show who started them.

Only Account Owners can remove users, you cannot remove yourself, and the last Account Owner cannot be removed.

Multi-tenant access

If your account has multiple tenants, users with custom access can have different roles in different tenants. For example, a user could be an Admin in the "Production" tenant but Read Only in the "Development" tenant.

An MSP Technician or MSP Read Only user on all tenants can also be given a higher role on one particular tenant; the higher role applies there. Users can switch between their assigned tenants using the tenant selector in the sidebar.