Axcient Help Center

How to Create a New Organization

You can create organizations and suborganizations for each of your customers. You can also create an organization for internal use.

To create an organization:

  1. In the Organization navigation menu, select the organization under which you want to create the new organization. For example, if you want to create a new organization under the master organization, select the master organization. The selected organization displays.

  2. Click the Organization button in the Organization navigation menu.

    0300003F.png

    The Organization Settings page displays.

  3. In the Organization Settings page, enter information into the Create an Organization section, including:

    1. In the read-only Parent Organization field, view the name of the higher-level organization. If you want to change where your new organization will be created within your organization hierarchy, use the Organization navigation menu to select the parent organization. For example, if you want to create an organization under the master organization, select the name of your master organization.

    2. In the Organization Name field, enter a descriptive title for the organization.

    3. Select the Trial Mode checkbox if the organization should be created as a trial for a customer. Trials expire after a specified number of days.

    4. In the Trial Until field, select the date on which the trial should expire for the customer, if applicable. If you select a date in the past, the trial to expire immediately, and lock out users.

    5. In the Hostname field, enter a unique URL that will be used when linking to the organization. Links to resources and shares will be prepended with this hostname (for example, customer.syncedtool.com). The Hostname field value can be edited after you create an organization.

    6. In the Organization Slug field, enter a unique identifier, which will be used to link to your organization (for example, customer.syncedtool.com/customer-organization). The Organization Slug field value cannot be edited after you create an organization.

    7. In the Description field, provide a description of the organization that can be used to organize and identify the organization.

    8. In the Contact Email field, enter the email address that will be used as the main contact for the organization.

    9. In the Default Language field, select the preferred site language for the organization, which controls the language settings displayed in the web portal and mobile apps, as well as number formatting. Leave this field blank to use the default language set for the system.

    10. In the Default Timezone field, select the preferred timezone for the organization, which affects dates and times displayed across the system. Leave this field blank to use the default timezone for the system.

      03000040.png
  4. In the Organization Policies section of the page, configure policies for this new organization, including:

    1. In the Space Quota field, set the space limit for the organization. Space quota values must be greater than 0 and less than 10000000. As a best practice, ensure that this limit is enough to account for personal files and folders, Team Shares, backups, deleted files and folders, revisions, and so forth. The sync process will stop if this limit is reached. Additionally, you might consider configuring an alert so that you are notified when the organization is reaching its set limit. For more information, please reference the How to Create Activity Alerts section of this guide.

    2. In the Parent is Using area, view the amount of space used by the parent organization, if applicable. This number will help you understand how much data is available for this new organization.

    3. In the Max File Size field, set the maximum size of individual files that can be uploaded into the system through desktop clients, mobile apps, and the web portal. By default, this is set to 300MB.

    4. In the Excluded Extensions field, enter fileextensions that you want added to the list of default excluded extensions, making sure that each extension is separated by a comma. Files with excluded extensions cannot be synced by the system. If an excluded extension is upload through the web portal, end users will receive an error messaging notifying them that their file is on the exclusion list.

    5. In the Max Number of Users field, enter a user limit that will be allowed for the organization. Alternatively, enter 0, which represents an unlimited number of users. Suborganizations cannot exceed the maximum number of users set for the parent organization.

    6. Select the Allow Creation of Suborganizations checkbox to allow child organizations to be created under the organization. A suborganization will inherit this policy from its parent.

    7. In the Max Number of Suborganizations field, set the maximum number of child organizations allowed under the higher-level organization. Alternatively, leave the field blank to allow an unlimited number of suborganizations. A suborganization will inherit this policy from its parent.

    8. Select the Enable Service Plans checkbox to allow the creation of service plans. A suborganization will inherit this policy from its parent.

    9. Select the Enable Branding checkbox to allow custom styles and logos for the organization. A suborganization will inherit this policy from its parent.

    10. Select the WebDAV Support checkbox to support WebDAV connections, which is another way for end users to view and edit files—both personal and through Team Shares—located in the cloud. WebDAV is useful when you do not want local copies of large files being stored on external machines. For more information, please reference the End User Guide. A suborganization will inherit this policy from its parent.

    11. Select the Backup Creation checkbox to allow administrators to create backups from the administrative web portal. A suborganization will inherit this policy from its parent.

    12. Select the File Server Enablement checkbox to allow machines to be cloud-enabled. With File Server Enablement, you can keep the existing file structure on the server while allowing remote access to files and folders.

    13. Select the Show PSA Tab checkbox to give access to the PSA tab in the administrative web portal, which is located under the Settings tab. In the PSA tab, professional services automated systems—such as ConnectWise and Autotask—can be integrated with x360Sync. A suborganization will inherit this policy from its parent.

    14. Select the Show Authentication Tab checkbox to give access to the Authentication tab in the administrative web portal, which is located under the Settings tab. In the Authentication tab, authentication sources can be configured for the organization. A suborganization will inherit this policy from its parent.

    03000043.png
  5. In the User Settings section of the page, you can define the user rights granted to administrators and standard accounts, including:

    1. Select the Let Organization Admins Browse User Files checkbox to allow organization administrators to view data in files, folders, shares, and backups, which is required to restore end user files. A suborganization will inherit this policy from its parent.

    2. Select the Let Organization Admins Browse Remote Files checkbox to allow organization administrators to browse machines. Browsing machines is required when setting up backups or File Server Enablement. A suborganization will inherit this policy from its parent.

    3. Select the Let Organization Admins Create Users checkbox to allow organization administrators to generate new user accounts in the system. A suborganization will inherit this policy from its parent.

    4. Select the Allow Users to Create Their Own Backups checkbox to allow end users to configure backups from the web portal or from their local machine. A suborganization will inherit this policy from its parent.

    5. Select the Allow Users to Share Files checkbox to allow end users to send shares. A suborganization will inherit this policy from its parent.

    6. Select the Force New Share Links to Require Login checkbox to disable public shares, and require the use of secure shares for all members of the organization on all devices. This policy also applies to shared items sent through the Outlook add-in. Secure shares require a username and a password before the content can be accessed. If a secure share is sent to someone outside of the user's organization, a guest account will automatically be created for the recipient. This policy is only available if the Allow Users to Share Files policy is enabled. A suborganization will inherit this policy from its parent.

    7. Select the Enable Web Preview checkbox to enable the Web Preview tool for end users. This feature allows users to preview content in the web portal and on mobile devices.

    8. Select the Enable Web Editing checkbox to enable the Collaborative Web Editor feature for end users. This feature allows users to edit content collaboratively, in real time, from the web portal.

    9. If the organization has access to a commercial Microsoft 365 subscription, use the Microsoft 365 Integration section to configure integration preferences. Click the Enabled for Editing radio button to allow authenticated users to read and edit files using their Microsoft apps. Click the Enabled for Read-only radio button to allow authenticated users to read (but not edit) files using their Microsoft apps.

    10. Select the Allow Users to Overwrite Collisions checkbox to allow end users to resolve collisions by syncing their own local copy as the latest server revision.

    11. Select the Allow Users to Lock Files checkbox to allow users to lock and unlock files. If this policy is enabled at the master organization level, the policy will appear for each organization. Otherwise, this policy is set per organization.

    12. The Use Filesystem Permissions to Enforce Locks On field allows you to specify extensions on which you would like the desktop client to enforce locks through filesystem permissions (also called hard locks). This field is important for File Server Enablement environments where mapped drive users must be notified by the filesystem when a file is in use. When a lock is placed, the desktop client will change the NTFS permissions on Windows, or HFS Plus permissions on Mac, in order to prevent changes by other users. These permissions still allow administrators to modify files, but they prevent standard end users from doing so, and makes for a much stronger lock. This field can only be edited if you previously selected the Allow Users to Lock Files checkbox.

    13. In the Force Password Change After field, enter the number of days that end users can keep their passwords. End users with expired passwords will be required to change their passwords when logging into the web portal.

    14. Select the Require Two-Step Authentication checkbox to add an extra layer of security to user accounts. With Two-Step Authentication, end users will be sent an authentication code through a mobile authenticator app, text message, or email; they must then enter their authentication code, along with their username and password, before they can access the web portal or register a desktop client, the Outlook add-in, or a mobile device. They will also be required to set up a passcode for any of their registered mobile devices. End users must configure their own authentication settings. If you turn off this setting for an organization, end users must individually disable their own configuration settings. For more information, please reference the End User Guide.

      03000044.png
  6. In the File Trim Settings section of the page, you can define how the organization retains file revisions (file versions), including:

    1. Select the Allow Users to Roll Back Revisions checkbox to give end users access to the Revision Rollback feature. If this policy is turned off, administrators will still retain the ability to utilize this feature for end user support.

    2. Select the Allow Users to Erase Revisions checkbox to allow end users to delete previous revisions of files within the system.

    3. Select the Auto-Erase Revisions checkbox to automatically delete previous revisions of files within the system. If this option is selected, you will need to enter the number of days that revisions should be stored. By default, the system retains all revisions.

    4. In the Erase Revisions for Files Unchanged In field, enter the number of days that revisions should be stored for unchanged files, if you previously selected the option to auto-erase revisions. By default, the system retains all revisions.

      03000045.png
  7. In the File Purge Settings section of the page, you can define how the organization retains deleted files, including:

    1. Select the Allow Users to Erase Deleted Files checkbox to allow end users to permanently remove files that have been deleted from the system.

    2. Select the Auto-Erase Deleted Files checkbox to automatically remove deleted files from the system after a specified number of days. If you select this option, you will need to specify the number of days that deleted files should be stored before being erased. By default, the system retains all deleted files.

    3. In the Erase Deleted Files After field, enter the number of days the deleted files should be stored before being removed, if you previously selected the option to auto-erase deleted files. By default, the system retains all deleted files.

      03000046.png
  8. In the Backup Settings section of the page, you can define how the organization retains files and revisions in backups, including:

    1. Select the Auto-Erase Revisions checkbox to automatically delete previous versions of files within backups. If this option is selected, you will need to enter the number of days that revisions should be stored.

    2. In the Erase Revisions for Files Unchanged In field, enter the number of days the that revisions should be stored for unchanged files in backups, if you previously selected the option to auto-erase revisions.

    3. Select the Auto-Erase Deleted Files checkbox to automatically remove deleted files from backups after a specified number of days. If you select this option, you will need to specify the number of days that deleted files should be stored before being erased.

    4. In the Erase Deleted Files After field, enter the number of days the deleted files should be stored before being removed from a backup, if you previously selected the option to auto-erase deleted files.

      Backup Settings.png
  9. In the API Token Settings section, use the Deactivate API Tokens After field to enter the number of hours that an API token should be set as active. By default, API tokens expire after 30 days.

    Note: API tokens expire immediately after initial use for certain sessions initiated from the desktop client, including:

    • Launching the web portal

    • Viewing an item in the web portal

    • Backing up a folder

    • Sharing a link

    • Viewing revision

    In these instances, API tokens will expire immediately after they are used, allowing desktop clients to securely connect to the web portal without requiring a username and password. API tokens for other sessions, including mobile and Outlook connections, will expire according to your API policy settings.

    30days.png
  10. In the Bandwidth Settings section of the page, configure bandwidth settings. For example:

    1. Select the Throttle Bandwidth checkbox to help regulate traffic and minimize bandwidth congestion. Restricting bandwidth will mitigate the impact that large files and shares might have on business-critical applications. You can also restrict bandwidth on individual machines.

    2. Select the Enable Throttle Exception checkbox to configure times when bandwidth throttling is not enabled. If you select this option, you will be prompted to specify a time period during which exceptions will be scheduled.

      03000047.png
  11. Click the Save button when you are finished. Your organization is now created.