Previous Topic

Next Topic

Book Contents

Book Index

SysAdmin Dashboard (Organizations Page)

  1. Sign on as SysAdmin.
  2. In the left navigation pane, click ORGS.

    The Organizations page opens.

    SysAdmins use the Organization Portal to Configure System-wide or Org-specific Settings

    Item

    UI Control(s)

    Description

    System Organization (root org settings)

    • Used by SysAdmins to administer system-wide settings and create and maintain other organizations.
    • Always present, cannot be deleted, and does not count against the number of organizations for which the system is licensed.
    • Not used to add users or transfer files.

    Licensed Organizations

    (List of orgs defined in this MOVEit Transfer deployment)

    • Includes all other MOVEit Transfer Organizations.
    • Each organization has its own data store, encryption scheme, and security preferences.
    • Organizations do not share information with each other.

    [Org Column Data]

    • Name: The name of the organization. Used throughout the application.
    • ID: The unique four-digit ID of the organization. Rarely exposed except when used in WebPosts.
    • Users: The current number of users (active and inactive) in this organization.
    • Folders: The current number of folders in an organization.
    • Files: The current number of files stored in an organization.

    Actions

    DMZ90_icon_pencil Edit. Opens the Organizational Profile

    DMZ90_icon_delete Delete: Deletes this Organization. You are prompted to confirm the deletion.

    DMZ90_icon_ActAsAdmin Act as Admin. Allows the SysAdmin to act as an Admin of the organization, to perform tasks such as selecting organization colors or setting up IP access lists.

    TIP Use MOVEit Transfer Organizations to organize and apply policies at the company, business unit, group, or team level. The concept of an Organization in MOVEit Transfer enables you to organize users, user interaction, and site information assurance according to org-level settings that implement policies within MOVEit Transfer.

Deciding when Multiple Organizations are Required

Create multiple Organizations when you want to enforce different policies based on partner status, business unit, or team requirements. For example, an organization that is highly collaborative might have looser controls, secure folder sharing that encourages user-level sharing with temp users, and so on. Less collaborative, business critical information, might have stricter Org-level controls, blocking data-loss prevention rules, and so on.

Examples

Multi org case: Standard Bank Services purchases MOVEit Transfer to provide secure data transport and collection services for three partner banks. Standard Bank Services wants to prevent any partner bank from accessing the information that any of the other banks have collected. Each of the three banks uses a distinct MOVEit Transfer organization. Partner banks have multiple MOVEit Transfer Groups, Group Admins, and Admin-level users for the Orgs they operate in. Standard Bank Services provides system level services.

Single org case: The Standard Auto Manufacturer company purchases MOVEit Transfer to receive purchase orders, price sheets and other information that requires built-in data integrity, access summaries, and audit logs. The manufacturer defines vendors as distinct MOVEit Transfer users (Temp and Regular users, no Admins) with access only to specific folders. Each user has specific, locked, inherited, home folder permissions. MOVEit Transfer users leveraged by these external vendors operate under strict policies defined within a single org.

Setup and Maintenance

Only SysAdmins can add or delete Organizations. Both SysAdmins and Administrators can configure Organizations, but some information, such as Name, Minimum SSL Strength, can only be configured by SysAdmins.