Microsoft Entra ID
Enable Microsoft SSO in Pickit’s admin settings and complete the Microsoft administrator consent. Microsoft authenticates each user with their existing work account; Pickit then establishes their session.
Built on Microsoft Azure, with Microsoft Entra ID and SAML sign-in, delegated content connections and access through API and MCP. Here’s how the parts fit together.
Let employees sign in with their organization’s account, then use Pickit’s permissions to decide which libraries and content they can access.
Enable Microsoft SSO in Pickit’s admin settings and complete the Microsoft administrator consent. Microsoft authenticates each user with their existing work account; Pickit then establishes their session.
Your identity provider signs the user in and sends a signed SAML assertion for Pickit to validate. Pickit helps your IT team configure metadata and sign-in settings for providers such as Okta.
Assign content access in Pickit for your administrators, employees and external audiences. A successful sign-in identifies a user; library and collection permissions determine what they can use.
Pickit runs as a cloud service on Microsoft Azure. Your team manages content, identity and access while Pickit operates the platform and its supporting services.
Microsoft Azure provides the hosting foundation for the Pickit service, with Azure Blob Storage used for asset storage.
Review Pickit’s security overview for information about data protection, operational access, monitoring and backups. Bring your organization’s requirements into the technical review.
Pickit supports Model Context Protocol (MCP), connecting your library to ChatGPT, Claude and Microsoft Copilot. Users authorize the connection through OAuth with their Pickit account to find assets, read documents and retrieve brand guidance.
Use the Pickit API to work with files, collections and metadata from your own application or service.
Explore the Pickit APIBring your identity administrator and content owner into the same plan. Validate the complete task with a representative user before expanding access.
Agree your provider, tenant and user lifecycle. Test sign-in with an ordinary user account.
Choose content owners, audiences and any source connections. Confirm who can find and use the material.
Assign the Office add-in through Microsoft 365 Integrated apps, or plan desktop installation separately. Test the app and content access together.
Bring your identity provider, content sources and target apps. We’ll help connect them to a practical plan.