Permissions FAQ

The My Permissions page displays the business e-mail to which your permissions have been assigned in the User Information box.

It also displays your assigned VLSC permission roles by Licensing ID in the Current Permissions table.

You can choose to display active or both active and inactive Licensing IDs in the table.

The Parent Program and - if it exists - the Microsoft Business and Services Agreement (MBSA) under which the Licensing ID was issued is listed for each item in the table.

You cannot add or remove roles (e.g. Software Assurance Manager or Online Service Manager) for any Licensing IDs in the Current Permissions table. However, you can completely remove a Licensing ID from your permission set if you believe that access has been incorrectly or inappropriately assigned, except if:

• You are listed as the Notices Correspondent or Primary Contact for the Licensing ID you are trying to remove.
• You are listed as the Notices Correspondent or Primary Contact for a legacy Microsoft Business and Services Agreement (MBSA) or on an Enterprise or Select Parent Agreement because the Licensing Info role is retained for all Child Licensing IDs of the MBSA or Parent Program. For more information, see the Administrator FAQ regarding Administrator Inheritance and deciding to Opt In or Opt Out as an Administrator of Child Licensing IDs.

To completely remove a Licensing ID from your permission set:

1. Go to VLSC My Permissions page
2. Locate the Licensing ID you want to remove in the Current Permissions table.
3. Click the Remove icon associated with the Licensing ID (the red X located in the left column of the row).

If you are signed in to the VLSC and Licensing IDs for your organization are not displayed, you may need to request access to your Licensing IDs by using the Request Permissions procedure described above.

1. Visit the Volume License Service Center (VLSC) and sign in.
2. Click on the Administration button and then on Request Permissions link.
3. Select the program type and enter the enrollment number or Authorization/License number.

1. Select the desired permissions.
2. Enter comments (optional).
3. Click Submit.

The Agreement Administrator will then receive notification of the request. To approve or deny request for permission, the VLSC Agreement Administrator should sign into VLSC, go to Administration, and click Manage Users.

1. View the Request in the Pending Request section of the page.
2. Click the Request Number.
3. Deny or accept the request to view license, add an optional note
4. Click OK to complete the changes.

If approved, the requestor can manage tasks related to the Licensing ID immediately.

It is rare that an organization has only one Administrator to manage VLSC access for all Licensing IDs. In large companies, there may be fifty or more individuals with Administrator access to hundreds of Licensing IDs.

By entering a specific Licensing ID on the Permission Request form, the VLSC is able to send your request to select Administrators with sufficient permissions to process your request.

For privacy reasons, we cannot post the names of Administrators associated with your company or organization.

If you do not know the identity of your Administrator, try the Request Permissions procedure described above.

The VLSC routes your request to the appropriate Administrators.

Alternatively, consult your with your organization's Purchasing, IT or Finance departments as they may be able to confirm the licensing information that you need or be able to identity your Microsoft Reseller from your organization's purchasing records."

See the following FAQ about managing user permissions.

If you are an Administrator, see the Administrator FAQ for information about adding new VLSC users, adding or removing permissions for existing users, responding to Permission Requests, Administrator Inheritance, and other issues specific to VLSC Administrators.

Administrators can perform any action related to an agreement using the VLSC with no restrictions.

Users who are assigned limited roles can perform only those actions associated with the assigned role. For example, users assigned the Download role can download licensed software only. They are not able to access Product Keys or perform other actions related to the agreement.

This is not a good practice. It creates the potential for one user to make changes to a password or permissions that negatively impact other users signing in with the same email address.

Each employee should access the VLSC with their own work or school account (WSA) associated with their individual work email address.

A permission role determines what you can or cannot do when using the VLSC to manage a specific Licensing ID (Select / Enterprise enrollment, Select Plus Customer Number, Open Value License, or Open License Authorization).

You may be assigned more than one permission role per Licensing ID that you have access to.

Your assigned roles may differ between Licensing IDs.

There are seven permission roles that can be assigned to a Licensing ID in the VLSC. Available roles may vary by Licensing ID.

The following table outlines allowable actions by permission role.

Yes. Resellers can be assigned a limited set of permissions to manage a specific Open License agreement on behalf of the customer, including the right to view license information, download licensed software, access Product Keys, view a Software Assurance Summary, and view or manage Microsoft subscriptions.

VLSC customers may also Contact Us by phone or by Web Form. Microsoft will respond to Web Form submissions within 24 hours.