Sign-in and app deployment for your organization.
Pickit supports Microsoft sign-in, Google Workspace and SAML, including Okta. Deploy the Office add-in through Microsoft 365 or install the desktop app separately. Plan sign-in, content access and app installation as three parts of the rollout.
Sign-in, permissions and installation.
Choose sign-in and define who gets access.
Connect your organization’s identity provider and test that the intended users can sign in. Permissions to content in Pickit are set separately.
Google Workspace
Connect the intended workspace and domain. Set permitted users and review how automatic invitations are configured.
SAML and Okta
Exchange metadata and configure login and SAML assertions with your identity administrator. Then test sign-in and access with a user account.
Agree who needs access.
List the people in the first release: content administrators, employee users and any external recipients. Define their tasks and the material each group should receive.
Review sign-in, app deployment, content permissions and source connections separately with your IT team and Pickit. Agree the technical assistance upfront; your IT team handles approvals and deployment. Installing an add-in does not by itself grant Pickit content access.
Connect Microsoft sign-in deliberately.
Pickit supports sign-in with existing Microsoft accounts. A Pickit administrator enables the connection in account settings and completes the Microsoft administrator sign-in and consent process.
Review the target tenant, administrative responsibilities and how users and groups will be maintained. Include a joiner and leaver scenario in the access review.
Deploy the relevant application.
For the Office add-in, Microsoft 365 administrators can use Integrated apps in the admin center to assign the manifest to selected users or groups. Confirm the target Office clients and allow time for the assignment to appear.
A desktop installation is a separate route. Choose the supported Windows or macOS application and plan installation with your IT team; an Office add-in assignment does not install the desktop app.
Test the full task, then hand it over.
Use a representative account to sign in, locate the intended content and complete the relevant insertion, viewing or download action. Test the actual client people will use, not only the administrator's web session.
Record who owns identity, app deployment, source connections and content maintenance. Give users a support route and agree how the setup will be reviewed when roles, groups or applications change.
What the Microsoft setup covers
- Identity
- Microsoft SSO configured by a Pickit administrator with Microsoft admin access.
- Office rollout
- Office add-in manifest assigned through Microsoft 365 Integrated apps.
- Content access
- Pickit account and permissions configured for the intended audience.
ICA Gruppen
ICA's published implementation combined PowerPoint access, Microsoft identity and directory groups. The story also describes Pickit supporting its IT team during deployment.
Read the customer storyA few useful answers.
Is SSO the same as automatic user provisioning?
No. SSO handles sign-in. User and group lifecycle behavior needs its own setup review; enabling Microsoft SSO alone does not establish SCIM provisioning or silent sign-in in every application.
Will deployment reach every employee immediately?
Microsoft add-in assignments can take time to appear. Check eligible users, direct group membership and the supported Office client, then validate a representative account before a wider introduction.
Can we start with one team?
Yes. A selected audience lets you check identity, content permissions and the end-to-end task before expanding the rollout.
Bring IT and the content owner into the same plan.
We can review the first audience, identity requirements and application workflow before a wider rollout.