Private cloud document management

Keep control of every file you store and share.

InOutShare gives organisations a governed workspace for private storage, document access, controlled downloads, client review and complete activity evidence.

InOutShare product screenshot

Replace this canvas with the file workspace.

Organise
Control
Approve

Private storage

Local, S3 or managed cloud

Policy access

Identity, device and network rules

External review

Sharing, approval and signature

Complete evidence

Actions, sessions and access history

Platform capabilities

Private files with enforceable controls.

The attached platform model connects storage and collaboration with identity, policy, approval and audit evidence.

01

Structured file workspace

Organise files in nested folders with ownership, paths, stars, metadata and storage quotas for each user.

02

Flexible storage providers

Operate on local storage, S3-compatible services or Cloudinary with configurable buckets, endpoints, roots and signed URL expiry.

03

Versioned documents

Retain numbered file versions, uploader, size, storage key, notes and document-edit session history.

04

Granular permissions

Apply allow, deny or inherited actions to individual users, roles and departments at file or folder level.

05

Controlled downloads

Require requests, reasons, reviewer decisions and OTP verification while applying access windows, limits and office-hour rules.

06

Preview & reading controls

Generate document previews, record read progress and enforce watermark, copy, print and download restrictions.

07

Secure sharing

Share files or folders with scoped permissions, recipients, start and expiry dates, access counts, IP controls and revocation history.

08

Approval & signature

Request document review, record approval or rejection and attach a typed, drawn or uploaded signature with signer evidence.

09

Adaptive authentication

Configure password rules, email OTP or TOTP, trusted devices, magic links, session limits, network rules and step-up actions.

10

Activity & access evidence

Record file, folder, sharing, permission, OTP and authentication events with user, session, device, IP and status context.

11

Notifications & email

Send security, download, sharing and administration messages with templates, delivery events, retry queues and user preferences.

12

Retention & recovery

Move deleted files and folders into managed trash with original paths, purge dates, restoration history and policy-based retention.

Product gallery

Add the product screens customers need to evaluate.

Four prepared image slots for the core file, sharing, security and approval experiences.

Main product image · 16:10

File workspace

Add the main folder and file-management interface here.

Image slot 02

02

Secure sharing

Add the recipient, permission and expiry configuration screen here.

Image slot 03

03

Security policies

Add authentication, trusted-device or access-policy management here.

Image slot 04

04

Approval & signature

Add the client review, document approval or signature experience here.

Controlled document journey

From upload to external approval.

Every step can carry the permissions, restrictions and evidence appropriate to the document.

01

Store

Upload to the selected provider and place the file in its governed folder.

02

Control

Apply role, department or user permissions and download policy.

03

Review

Preview, read or edit the document while retaining version context.

04

Share

Choose recipients, scope, expiry, access limits and permitted actions.

05

Approve

Capture client decision, confirmation and signature when required.

06

Evidence

Record access, changes, downloads, devices and notifications.

Security by policy

Apply stronger checks to higher-risk actions.

Authentication and access policies can be scoped by role, department or user and can consider time, network, location, device, browser, session count and requested action.

MFA & trusted devices

Email OTP, TOTP, recovery codes and device trust.

Session policy

Device, browser, network and concurrent-session controls.

Step-up approval

Require stronger authentication or review for sensitive actions.

Retention & recovery

Storage history, managed trash and policy-based purge dates.

InOutShare FAQs

Questions before you evaluate InOutShare.

Answers based on the storage, sharing and security workflows represented in the attached system.

Ask our product team
01Where can InOutShare store files?+

The platform can use local storage, S3-compatible storage or Cloudinary. Administrators can configure provider details, buckets, endpoints, root folders and signed-link expiry.

02Can access be controlled by department or role?+

Yes. File and folder permissions can target an individual user, role or department and can explicitly allow, deny or inherit actions.

03How are sensitive downloads controlled?+

Files can require a download request, reviewer approval and OTP verification. Policies can also limit download count, set expiry, restrict downloads to office hours and retain access evidence.

04Can external recipients review and sign documents?+

Yes. Shares can support client review, approval or rejection, confirmation text and required signatures, with signer name, email, IP, device evidence and signature hash.

05Does InOutShare support document preview and editing?+

Yes. The platform models generated previews, reading progress, document conversion jobs, edit sessions and new file versions, with optional office-server integration and autosave settings.

06Which security controls are available?+

The schema includes email OTP, TOTP, recovery codes, trusted devices, adaptive authentication, time and network restrictions, session controls, step-up actions, login risk records and comprehensive activity logs.

Start a conversation

Connect with our technology team.

Tell us what you are building, improving or exploring. Our team will review your requirements and respond directly by email.

Email our teaminfo@coderxpoint.com
Your enquiry is emailed securely and is not stored on this website.

All fields marked * are required.