Reusable destination
Give a production, research, finance, or operations team a durable place to receive repeat package deliveries.
Shared Inboxes
Secure file intake for teams and external partners.
Give approved senders a reusable destination for large-file deliveries. Shared Inboxes bring team roles, external upload access, notifications, and received packages together. They are built for file intake—not shared email conversations.
RIPTON CLOUD / Shared Inboxes
01
entry
Teams + partners
02
control
Inbox access
03
transfer
Approved upload
04
evidence
Received packages
Workflow example
One team. Repeat deliveries. A controlled file intake workflow.
Consider a production team receiving weekly packages from an external vendor. A Shared Inbox keeps the receiving destination attached to the team instead of a single employee.
- 1
The manager sets up intake
Create the team destination and assign managers and members. Decide who is responsible for reviewing outside access.
- 2
The vendor receives scoped access
Invite the collaborator or review their guest access request. Approval grants the supported upload scope, not general access to the workspace.
- 3
The team follows the package
Review received packages and notifications in the inbox. Manage invitations as the vendor relationship changes.
In your demonstration, ask to see the manager and external-sender experiences, a received package, and what happens after an invitation is removed.
Why it matters
Keep incoming files with the team that needs them.
Explicit responsibility
Separate manager, member, collaborator, and guest-request responsibilities instead of relying on one employee's links.
Package continuity
Keep received package visibility and notifications attached to the team destination as people and projects change.
How it works
How does a sender get permission to upload?
An internal owner manages the destination and its members. External senders use an invitation or an approved access request before receiving the supported upload scope.
- STEP 01
Create the inbox
Name the destination, define its purpose and status, and establish the internal ownership model.
- STEP 02
Assign the team
Add managers and members with the current shared-inbox roles.
- STEP 03
Approve external access
Invite a collaborator or review a guest access request before narrow upload access is issued.
- STEP 04
Receive and operate
Follow notifications, received packages, membership changes, invitation status, and inbox activity.
Capability detail
Who can manage access and follow deliveries?
Member roles
Attach internal users to a Shared Inbox with distinct responsibilities and supported in-place role updates.
External collaborators
Invite, resend or rotate, list, and remove approved external collaborator invitations.
Guest access review
Allow an external sender to request access and let an authorized operator approve or deny it before upload.
Package and notification context
See packages assigned to the destination and support member and collaborator notification workflows.
Operational evidence
A managed intake destination—not a general-purpose mailbox.
The Shared Inbox connects internal membership, external access, notifications, and received packages around a controlled transfer destination.
- Inbox status and ownership
- Members and role changes
- Invitations and access requests
- Received packages and notifications
Continue exploring
Related platform and solution pages.
Public links
Understand the scoped external entry experience.
Explore →Browser workspace
See how packages are prepared and followed.
Explore →Secure partner exchange
Apply Shared Inboxes to a repeat partner workflow.
Explore →Set up a Shared Inbox for vendor deliveries
Create the inbox, add members, publish the link, approve requests.
Explore →File upload portal
Let anyone send you large files without giving them an account.
Explore →Creative agencies
Footage from shoots and freelancers arriving as folders.
Explore →Frequently asked questions
Technical questions, answered plainly.
Does every external sender need a named-user account?
No. Supported external guests remain separate from the named-user directory and receive only the approved upload access.
Can a manager remove an external collaborator?
Yes. Current Shared Inbox controls support listing, rotating or resending, and removing collaborator invitations.
Is a Shared Inbox permanent storage?
No. It is a controlled destination and package-access workflow. Storage lifecycle, cataloging, archive policy, and records management remain separate responsibilities.
Evaluate the workflow
Model one recurring intake workflow as a Shared Inbox.
Bring the team, sender population, approval path, package type, and notifications you need. We will walk through the internal and external experience.