Organizations and Policies

A organization is an administrative unit for a set of users. It includes policies, storage resources, and permissions for those users. A single instance of an appliance can host multiple organizations. Once created organizations, also called tenants, are self-managed by their users and not accessible or even visible from other organizations on the same appliance.

An appliance administrator creates organizations and provides credentials for the first “Organization Administrator” who must log in to complete the setup of organization policies and users.

This document walks through creating an organization and setting up organization policies.

Create an Organization

Review User Package (Optional)

The File Fabric platform uses templates for organizations, in order for us to create our organization, we need to pick a template, before we do, let’s review.

Login as the Appliance Administrator.

Click “User Packages” and then click the pencil to modify “Organisation Cloud 20 Users” This is a good template to start from. Scroll down to the “Extra options” section and add “Content Search Enabled” and Dropfolders. Use “Crtl-Click“ to add to the selection.

Create Organization

Login as the Appliance Administrator.

In the hamburger menu, select “Users” and then “Add a User”.

On the Add a User screen create your Organization admin user. (This will also be your organization.)

  1. User Login: The Organization short name and superuser's username. We recommend the domain name of your company such as “”.
  2. E-mail: Email address of organizational admin, must be unique to the system, do not use your own.
  3. Password:
  4. Name (Company Name): Full organization name.
  5. Package: The user package template from earlier.
  6. We do not need to split the license between organizations, leave the last field empty.

Click Save.

Delete the sample accounts

This can be done by clicking the red “X”.

Adding Users

Users are managed per organization. The login name for a user is of the format username@orgname where orgname is the name given to your Organization.

Users can be authenticated against an internal user database or an identity management service. Out of the box support is provided for Active Directory, and SAML. Please contact us with other integration requirements.

For more information see Identity and Access Management or Adding / Managing Users.


Log out from the Appliance Admin, appladmin user, and log back in as the user you just created.

You will first see the “Add Storage Provider” screen. You have to add storage before you can continue. Select your provider and follow the instructions on the next couple of screens. There are many providers to choose from, but a CIFS share, google drive or S3 bucket are easy examples to get started with. Do not use a storage location with existing production data for the initial trial.

Once you have added your storage, Select Policies from Organization Menu:
There are of course a lot of different was to configure your organization based on your specific use case(s). In this example I will set them to what I think are good starting points.

User Governance

Enable personal clouds by toggling “Private User Clouds”. Enabling this will allow for both a per user home folder (Admin managed) and for users to add a personal drop box, or google drive into the SME file manager.

File Sharing Policy

Here I like to turn on most of the options in order to get a feel for the SME sharing features. See screenshot below.


See screenshot below for how to toggle the options on this page:


You can provide a key here and enable encryption for all data at rest. Note, if you do, you will not be able to access your data from outside of SME.


I enable versioning, it is a nice feature to have in case of conflicts or accidental end user overwrites and deletions.

Data Classifications

Leave the defaults here.

User Interface

Leave the defaults here.


Toggle “Send email notification for file comments:” to “To all members and file commentators”


Options for you to create your organizations specific here

At this stage you either create local users or you tie SME into your corporate directory.

Setting up shared storage and access.

Earlier we connected to our default storage, now let’s configure it.

Click File Manager

And navigate into your default storage provider, in my case it is a bucket called “smestoragesme”

Unless this is the name of the root share you want your end users to see, create a new folder inside the root. I created one called FinanceShare and one called EngineeringShare.

Right click the first folder and select Convert to Shared Team Folder

Then repeat for any other folder you have created and want to be a share root. By default, in SME, a shared folder is shared with no one (except the admins) so we have to modify permissions.

Go to the settings page for shared folders:

The default tab should be the Permissions tab:

Go ahead and select the permissions Icon (2)

In the popup windows (below) select the user or group from the dropdown (1), select the permissions (2), and click apply. (3)

When you are done with the permissions, for this share click close. (4)

Your initial setup is complete, now when a member of the Engineering group logs in, he or she will only see the EngineeringShare folder:

While the members of the finance group will see only FinanceShare.

For any questions or comments on this document, please contact