Manage in Pickit
Upload files to Pickit and maintain their versions, descriptions and audience access there.
Enterprise architecture
Fit Pickit into
your content architecture.
Understand how your chosen setup connects content sources, Pickit-managed material, audience access and distribution channels. Make storage, update behavior and ownership explicit before rollout.
How files reach Pickit
- A copy in Pickit
- An import can copy original files into Pickit-managed cloud storage. Content then no longer stays only in the source system. The connection determines when that copy is refreshed.
- An original kept externally
- Google-native documents stay in Google Drive and open at the source. Dropbox also offers an external-file option that keeps originals in Dropbox while Pickit stores their information. Source access and download behavior depend on the connection.
- A separate copy in someone’s work
- Downloading a file or inserting material into a presentation creates a separate copy. Later library updates do not change that copy.
Start where you are
Give your content
a clear path forward.
Connect existing sources
Import selected material from a supported source. The connection determines whether files are copied or referenced, and how later changes are handled.
Combine the two
Maintain some originals in Pickit and others in connected systems. Assign an update owner for each source.
Define the details together
Two architecture
decisions to make explicit.
Document source ownership and audience access before connecting the systems.
Know where the content lives
Map the files, metadata and source systems. Agree whether each connection imports files, brings previews into Pickit or uses another supported model, and who owns subsequent updates.
Separate source access from Pickit access
The account used to connect a source and the people who can use its content in Pickit are different decisions. Define the importing account, library permissions and intended audiences, then test representative users.
Connect your own content workflow.
Use Pickit’s public API when a supported custom connection is the right fit for your systems.
- Retrieve, search, filter and page through accessible files and collections.
- Upload a file through its source URL or update supported asset data.
- Use Pickit API credentials within the configured account and user permissions. MCP authorization is a separate connection.
A few useful answers.
Can Pickit connect to our existing DAM or storage system?
That depends on the system and workflow. Review the source, available connector, direction of data flow and required actions with Pickit. A conceptual architecture is not a promise of a native connector.
Does all content stay in our existing tenant?
No. Imports can create copies in Pickit-managed cloud storage. Some connections offer external-original options, with information and previews in Pickit. Check the selected connection’s storage and update model against your requirements.
How do identity and deployment fit in?
Supported SSO and centralized deployment can be part of your setup. Review your identity provider, access model and target applications together. Office add-in deployment and AI-client authorization are separate workflows.
What should we bring to an architecture discussion?
Your source systems, file types, content owners, audiences, identity provider and target applications. Include your security and data-processing requirements so the team can review the relevant documentation and configuration.
Agree the setup before scaling the experience.
Map your sources, access and update responsibilities around a representative workflow.