Use case

Loosen one space, not the whole site

Campaign work runs on layered design files, video cuts and agency exports. The marketing space overrides the global rule for those types only, and every other space stays as strict as it was.

Book a free demo Try free on Marketplace

The exception has a boundary

Recorded in a live Jira Cloud site. 4 minutes, no sound.

Where it goes wrong

The baseline is right. It is just wrong here.

A rule with no exception does not get followed. It gets worked around, and the workaround is worse.

Right everywhere, wrong in one place

Large design and video formats are kept out on purpose. Marketing is the one space where they are the work itself.

The exception costs a ticket

Someone asks an admin, waits, and explains it again next quarter. In the meantime the file goes somewhere else.

Assets leave the ticket

A transfer link in a comment becomes the delivery route. Nobody knows what is behind it or how long it stays alive.

The override

Allowed in one space only.

Pick the marketing space, pick the types it runs on, set them to Allowed and tick Override global configuration. The global rule is left untouched.

The exception has a boundary. An override is stored on the space, not on the site. No other space inherits it, now or later.
You can take it back. Remove the override and the space follows the global category again, from the next upload on.
Everything outside the list still goes. An exception for three formats is not an open door. The rest follows the rule it followed before.

Where the override sits in the settings

The file type settings, with a category set per type — One space overridden, the rest untouched.

What stays visible

An exception you can read back later.

The point of a space level override is that someone can check it. Both the rule and every removal under it are recorded.

The change is a row. Setting an override is written to the log with the person and the time, like any other configuration change.
So is every removal. A file outside the list is taken off the work item, the comment names the rule, and the log records it.
Reviewable later. Filter the log by time range, process and object type to look at the exception again later.

The Regulit log, one row per change — Configuration changes and removals in the same log.

How a type is matched

Type and extension. The stricter rule wins.

Design tools write the same format under several names. Regulit looks at the type Jira reports and at the file extension.

The extension counts too
When type and extension disagree, the stricter rule applies.
Jira reports the type
One file type can cover several mimetypes, so one entry handles every name a tool gives the format.
Missing types are added once
A Jira admin adds it under Create File Types, with mimetype, name and extension. From then on it is selectable in every space.

If the type is unknown

A format nobody has configured follows Setting for undefined file types, which ships as Needs approval. With storage connected, the first file of a new format waits for a decision. Without storage it is removed.

Creating a file type in Regulit, by extension or by mimetype

Questions about exceptions

Can one space be less strict than the site?

Yes. Set the type to Allowed in that space and tick Override global configuration.

Does the exception reach other spaces?

No. It applies to that one space.

Our format is not on the list.

A Jira admin adds it under Create File Types, with mimetype, name and extension.

Is there a size limit for large files?

No size rule. An allowed file stays at any size. Above 50 MB a file cannot be held for approval.

Is a file type we add checked by content?

No. A file type you add is matched on mimetype and extension only.

Read on

Two pages carry the rest.

This page argues the case for a space level exception. What the app does with the rule, and what it takes to switch it on, each have a page of their own.