Organizations
Managing the organizations on your domain
Last updated
Managing the organizations on your domain
Last updated
An organization is a way to categorize users for administration & management purposes. If you are a holding company that is a collection of multiple companies, you can consider creating an organization for each company. Assign an admin to each organization who then will have the privileges to perform user administration & management tasks for the users who are part of the organization.
Organizations: List of organizations and their hierarchy on your domain. The default organization is the single, top-level node. All other organizations you create become the βchildβ (sub-organization) nodes of the default organization. For example, a parent company might own 3 organizations with distinct internet domain names like help-docs.com, child1.help-docs.com & child2.help-docs.com, which can be modeled as 3 organizations under one MangoApps domain.
The MangoApps Domain URL is uniquely tied to the default organization. No other sub-organization can be created using the same domain. All child organizations must use a different domain URI.
Open Organization: This is the default option. Companies primarily use it to delegate user admin roles. This feature lets companies divide employees into multiple buckets and assign one or more administrators to manage the users of each bucket. Select this option if you:
Do NOT want to restrict users of one organization from following or messaging users of other organization,
Want content of one organization be accessible to members of other organizations.
Label for Organization: The text used for the default organization label. You can use "company" or any other text as the organization label.
Organization Name: Unique name that identifies the organization on your domain. Mostly seen in the users' list in the Manage Users tab.
Organization Domain: Your companyβs unique URL to access MangoApps. In most cases, it is formed from the portion after the β@" sign in your userβs company email address. For example, if you signup with john@help-docs.com it becomes help-docs.mangospring.com (on US data center) or help-docs.mangoapps.com (on any of the 4 international data centers). Another example is, if you signup with john@stateuniversity.edu, it becomes stateuniversity.mangospring.com (on US data center) or stateuniversity.mangoapps.com (on any of the 4 international data centers).
This domain URL is customizable for all our private cloud & on-premise customers. This domain also becomes the top level Organization in MangoApps.
The organization domain acts as the parameter for rerouting user invitation approvals to the network admins and organization admins (Admin Portal > Domain > General Settings > Invite, Signup & Login Settings > Employees to invite other employees > Moderated > Approvals are first routed to the organization admin based on user's domain email).
Organization Admin: Specifies the organization administrators who have permissions to manage users belonging to the organization. Organization admins can approve new user invite requests, reset passwords, deactivate users, etc. They CANNOT delete users. See Admin Roles for more information. Organization admins do not themselves need to belong to the organization they manage. There can be multiple organization admins for one organization.
Number of Seats Allocated: Allocated number of users that can be activated to use MangoApps per organization. More than the number of seats can be assigned, but only the number of seats specified can be activated at once. If youβve activated the maximum number of seats, you must first deactivate some of the existing seats before new seats can be activated. Leaving the field blank indicates that unlimited users can be allowed in this organization.
Allow Creation of Groups by Organization Members: If enabled, allows only the members of the organization to create groups.
Parent Organization: Specifies whether the organization can have βchildβ (sub-organizations).
Save Changes: Click the Save Changes button to save the modifications to the settings.
You can add "child" (sub-organizations) to the default top-level organization. A sub-organization can have sub-organizations if it the Parent Organization checkbox is marked for it. To add organizations:
Enter the name for the organization in the Organization Name text box. For example, enter "Child Organization 2".
Enter the domain for the organization in the Organization Domain text box. For example, enter "child2.help-docs.com".
Add the admins for the organization in the Organization Admins text box. This is an optional step.
Enter the number of seats allowed for the organization in the Number of Seats Allocated text box. This is an optional step.
Mark the Allow Creation of Groups by Organization Members checkbox to allow only members of the organization to create groups. This is an optional step.
Mark the Parent Organization checkbox to allow the organization to have "child" (sub-organizations).
Click the Save Changes button.
Repeat steps 1 through 8 to add more "child" organizations on your domain.
Refer to the video for more information Adding Organization.
Only network admins can create organizations in the domain.
To delete an organization:
Deleting an organization does NOT delete the members of the organization.
You CANNOT delete the default organization (first node).
You can move an organization to organizations which have been allowed to have "child" (sub-organizations). To reorder organization:
In the Move Organization pop-up, select the preferred organization and then click the Move button.
Refer to the video for more information Reordering Organization.
You can move a group of organization which has sub-organizations into another parent organization.
Departments manifest themselves in the User Portal and typically resemble your company departments like finance, hr, operations whereas organizations do NOT appear in the User Portal and can be entirely different from your company structure.
A βparentβ organization is one that is allowed to have "child" organizations (or sub-organizations). The default organization is, by default, a βParentβ organization.
When you provision user accounts (either by inviting users or by integrating with Active Directory) the users in the domain get assigned to an organization based on their email address automatically. This makes the organization setup fast and simple. As a network admin, you can change the userβs organization at any time.
Under this option:
A user can only belong to 1 or more organizations.
Organization admin for the organization and the network admin is responsible for user administration.
Parent organization admin can administer child organization users as well.
A user from one organization can follow any user from any other organization.
All content visibility is by default at the full company level. Further granular control to access content can be achieved by creating departments, projects, and groups within which fine-grained access rights can be setup for updates, files, wikis, posts, events, etc.
Click the Actions () button for the preferred organization and then click Add child organization.
Click the Actions () button for the preferred organization and then click the Delete option.
Click the Actions () button for the preferred organization and then click the Move option.