Organization options
Sjaak Velthoven avatar
Written by Sjaak Velthoven
Updated over a week ago

It is possible to request the following options to be set for your organization.

These options will apply to all projects owned by the organization.

This article contains information about the following topics:


Please contact support through the chat bubble or at if you wish to change the name of your organization.


Please contact for questions regarding your plan.
Your plan decides how many projects you can have at any moment in an organization.

Your plan also decides when new projects expire.

Defaults for new projects

Document download title option

If you download a single document the filename will always be the original file name.

If you download multiple documents the filenames will be the names of the documents.

With this option you can configure what filename you will get when you download multiple documents. This can be useful in combination with the naming convention and for overwriting documents that have the same name instead of with a different revision number every time.


The name of the project is testproject.

Two files are uploaded with two revisions each:

test01.pdf and test02.pdf

The names of the documents are then changed to:

changed01.pdf and changed02.pdf

Default download behavior:

If you download these documents one for one they will always be named

test01.pdf and test02.pdf

If you download both these documents at the same time they will by default be called changed01.pdf and changed02.pdf

This is what can be changed with the following options:


Revision file name

Note that this is the same as when downloading a single file so the names will be consistent if you choose this option.

<Original file name>.<Extension>

test01.pdf and test02.pdf

Document title - default

<Document name>.<Extension>

changed01.pdf and changed02.pdf

Document title with revision number

<Document name><Revision number>.<Extension>

changed01.pdf #2 and changed02.pdf #2

Project title with Document title and Revision number

<Project name><Document name><Revision number>.<Extension>

testproject changed01.pdf #2 and testproject changed02.pdf #2

Downloading of infected documents

Quarantine handling for infected files in owned projects.

If a document is found to be infected, by default, it can be downloaded. The user will get a warning that this document includes a virus. An option can be set per organization that makes it so no-one, not even administrators will be able to download infected documents.


Warn on download - default

Block download

Models as documents

If this feature is turned on all new projects that are made in the organization will have the Models as documents feature turned enabled.

Note: 24 November: This feature will be enabled for all new organizations.

We will support the old view for about a year before all projects are migrated.

Document upload draft option

If approval flow has been enabled and there are draft statuses in document settings the upload as draft checkbox is checked by default upon document upload.

Per request this can this checkbox can be set to unchecked by default for all projects in an organization.


Users can be added as members or owners of an organization.


Owners of organizations can see an overview of the organization in the organization tool.

In this tool they will be able to:

Move projects to other organizations they own (Archives are often a separate organizations)
Create new projects within the organization if your plan allows that.
Delete projects owned by the organization.

Add organization members to projects without inviting them.

Invite users to organization projects without having to be part of the project.

It is recommended that this organization owners are kept few as projects do not have to be moved often.


Members of organizations can easily be added to the organizations projects by organization owners.

Project owner rules

Enforce that all users require MFA

Enterprise customers can request the enforcement of MFA for users participating in their projects. With this option all users are required to have MFA set up to join projects that are owned by your organization.

Internal SSO users do not require MFA

Enterprise customers can request to set up Single Sign-On.
There is a fee involved as it takes our developers some time to set up the configuration.

What does this rule do?
By default users who log in with SSO and users who log in normally are treated the same.
If MFA is enforced for an organization both regular users and SSO users therefore have to insert the MFA code to log in and access the project.
If this option is checked for an organization SSO users do not have to use MFA to access the project.
Regular users would still have to input the MFA code while SSO users could log in without having to use the code.

What is SSO?
Single Sign-On allows the user to log in once and access services without re-entering authentication factors.

With this option you can make it so users for your organization do not have to set up MFA.

Users from different organizations that are part of your organizations projects will still have to have MFA on if the option above is enabled.

Setting up SSO:
It is possible to set up SSO with any SSO provider as it is a standardized process please find some of the most common SSO providers below:

Microsoft Active Directory:
You will need to ask your system administrator to set up a new Azure Enterprise Application in your Azure AD environment using SAML authentication with the following details:

Assertion Consumer Service (ACS) URL:

Note: The sign-on URL, should you need it is the following:

When that is done your system administrator will have to get back to us with the App Federation Metadata URL and Federation Metadata XML for the new application.


Set up SSO as in this article

Test users:

Once the SSO setup is configured, please supply a list of test users for which the SSO can be enabled first so you can see how the SSO will work for them.

Once the test users have been tested the rest of the users can be enabled.

Black and Whitelist:

It is also possible to configure a black/whitelist:
For example:
All users except: X, Y and etc. should be allowed to log in with SSO
Only X, Y and etc. should be allowed to log in with SSO
This information will have to be supplied in addition to the XML file as specified above.

Disable public sharing feature

This option lets you disable the public sharing feature for all projects in your organization.

If this option is enabled it will no longer be possible to:


You can request that a domain is added to your organization.

If a domain has been registered with your organization the option "add from domain" will appear on the users page of your organization in the organization tool.

This will let you add users from your organization to your projects without having to invite them through email invitations.
If you do not find a user from your organization this will most likely be because they have not made a Catenda account yet and we do not have them in our system.

Users from your domain that do not have accounts yet will have to be invited the regular way so they can join the project and make an account.

Users from domains that have not been added will still have to be invited with the regular email invitation.

Did this answer your question?