Settings page

Settings holds the rules of one application’s storage. A backend can read and change the same values with files:config.manage; every key, default and range is in the settings reference. This page walks through the sections for administrators.

Prerequisite: the CCS Identity Server.The File Service runs on your Identity Server. It owns your users, tenants, applications, roles, clients and tokens; the service owns none of them.

Your role needs the permission for the page, granted by the tenant owner on the console's Permissions page, and Files must be switched on for the application. See who can open which page.

New to it? Read the Identity Server documentation (opens in a new tab).

Permission: files.settings.manage

Storage

• Quota: unlimited (the tenant’s quota applies) or a size for this application. It must fit in what the tenant quota leaves after the other applications’ quotas.
• Largest file: default 2 GiB, never above the tenant’s ceiling or the platform maximum of 5 GiB.
• Allowed types: a list of MIME types and families such as image/*, or * for everything (the default). Up to 100 entries.

Named upload policies

A named policy narrows the allowed types and the size for uploads that ask for it by name, for example avatar (images, 5 MB) or chat (images and videos). Products that upload into this application choose the policy; you decide what it allows, here. A policy never allows more than the application itself. Up to 20 policies.

CCS Chat asks for the policy named chat for the photos, videos and files people attach to messages. Without a chat policy, Chat’s uploads follow the application’s own allowed types and largest file. Where Chat keeps those files and what else applies to them is on Media in Chat.

Checks and processing

• When the bytes are not the declared type: refuse the file (the default), keep it with the detected type, or keep the declared type.
• Malware scanning: block downloads until the scan is clean (the default), allow downloads during the scan, or do not scan; and what happens to a file whose scan fails (blocked by default) or that is too large to scan (allowed by default). See Malware scanning.
• Previews: thumbnails and previews of images, PDFs and videos, and the playable MP4 versions of videos, on by default.
• Text extraction: the text of documents for searching inside them, on by default.
• Image metadata: removed by default (camera, location and the rest of the EXIF data); keep it if your application needs it.

Visibility, owners and approvals

• Default visibility of new files: private, application, or public.
• Public files: off by default. When on (and the tenant allows it), files can get a stable link anyone can open.
• What owners may do with their own files: by default view, download, edit, share and delete. Narrow it to view and download when only your backend should change files.
• Owners may purge their own files from the trash.
• Approvals: the draft, in review, approved, rejected and archived statuses; see Approvals.

Share links

On or off, the longest expiry a link may have (0 switches links off), and your own host for share links instead of the service’s.

Retention and links

• Trash: how long deleted items can be restored, default 30 days.
• Versions: how many versions each file keeps (default 10) and for how long.
• Download links: how long minted download and preview links live, default 15 minutes.

Managed lists

The categories and departments lists: values with a label, active or not, and whether the list is enforced. An enforced list accepts only its active values on uploads and edits (taxonomy_value_invalid).

Webhook

An HTTPS endpoint of your backend that receives the file events of this application, signed with a secret: the URL, the events, the secret (write-only: once set it can only be replaced) and whether it is active. Saving sends the endpoint a test call first and saves only when it answers. Your developers set up the endpoint; see Webhooks.

Note

Saving checks every value against its range and the tenant’s ceilings and shows every problem at once. Every saved change is in the audit log as settings.updated, with the values before and after.