During onboarding (and other QorusDocs professional services engagements), the Product Specialist completes required system configuration tasks within the customer’s Microsoft environment. This access supports our “set up first, then train” approach, which aims to complete initial configuration before user training. This ensures customers see value quickly.
The customer can choose one of the following approaches to provide the access needed.
1. Dedicated Microsoft-Licenced user account (Preferred)
The customer creates a dedicated, Microsoft-licensed user account inside its tenant for the Product Specialist. This is often achieved by going through your organization’s contractor account/external access request process.
Benefits
- Faster onboarding and configuration
- Stronger launch readiness
- Earlier validation of the end-to-end solution
- More accurate setup and testing
- Improved quality and consistency of configuration
- Reduced workload for customer IT teams
- Fewer handoffs and less confusion
- Better use of training time
- Reduced onboarding fatigue
2. Guest User access
The customer adds the Product Specialist as a guest user in the tenant.
Known limitations/issues
- Microsoft can restrict guest users from completing some configuration tasks (for example, taxonomy/term store configuration that supports managed metadata filters). Where these restrictions apply, the customer will need to perform those steps internally.
- This can delay launch readiness.
Access requirements
Whichever of the above options is selected, access is required as follows:
- Site owner level permission within the QorusDocs SharePoint Site.
- Contributor permission to the QorusDocs Term Group in the SharePoint Term Store.
How access affects Onboarding timelines
Without appropriate access, the customer will need to complete more configuration tasks internally, which can extend project times significantly and lead to configuration errors.
Comments
Article is closed for comments.