Secure Folder Hierarchies and Roles
Define who can upload, view, edit, download or share assets, who can see or edit individual metadata fields, and who can use workflow or administration tools.
Book a DemoControl who can view, edit, download, share, search and administer content, while audit logs, secure hosting and identity integration support wider governance requirements.

iBase combines folder hierarchy security, user roles, field-level control and workflow permissions so access can match the reality of complex collections.
Define who can upload, view, edit, download or share assets, who can see or edit individual metadata fields, and who can use workflow or administration tools.
Integrate with Microsoft Entra ID/Azure AD and other single sign-on approaches so authentication aligns with organisational access policies.
Grant authorised websites, CMS platforms and applications tightly controlled API rights, shaped by folder-level permissions and data access needs so external systems only reach approved files and metadata.
Security is not only a login screen. iBase provides activity records, hosting choices and compliance evidence that help buyers and administrators understand how assets are protected.
Cloud deployments can run in a UK-based AWS environment with resilient asset storage, regular backups, penetration checks against current standards and optional access restrictions by approved IP ranges or domains.
Record user, date, time, IP address, asset and outcome for actions including uploading, downloading, searching and editing, with reporting and export options for review.
Implementation planning can document backup approach, recovery requirements and operational responsibilities for critical assets.
GDPR documentation, IASME and Cyber Essentials signals give buyers routes to compliance evidence during supplier review.
Permission models, application access, audit visibility and hosting choices can be configured around internal policy, collection sensitivity and buyer assurance needs.
Roles and secure folders keep different contributors, administrators and viewers in their proper lanes.
Audit trails help teams review use, investigate activity and provide evidence for governance conversations.
APIs and external systems can be granted access without opening the whole repository.