Organization, OU, Groups, Accounts & Roles introduction
Initially when you start with Twake, all your users are placed in a single Organizational Unit which represents your Organization. All settings you make in the Twake Admin Console apply to this top-level organization and therefore to all users in your Twake Account.
As an Organizational Admin of your Twake, you control which services and features are available to users in your organization. To apply policies for users or manage their settings, use your Twake Admin Console to place users into organizational units. Then turn on or off services and choose service settings for each organizational unit. You can also turn on services just for a Group of users within an organizational unit.
Twake is a Multitenancy digital workplace. If you are using a managed Twake (ie SaaS offer provided by a cloud provider), your Organization is a dedicated Tenant of the Twake Instance managed by your provider. With your Twake Account, you can manage users, services and settings inside your dedicated tenant.
If you plan to install your own Twake Instance, you will process the installation as the Platform Super Administrator. The installation process will ask you to create a first Tenant corresponding to your main Organization and a first Organizational Admin.
Comparison between Groups and Organizational Units
+—————————+—————————————————————+———————————————-+
| | GROUPS or TEAMS | ORGANIZATIONAL UNITS |
+===========================+===============================================================+==============================================+
| Function | * Turn ON (only) services or features | * Turn on/off services or features |
| | * Configure a limited set of settings on service or feature | * Configure service or feature settings |
+—————————+—————————————–+——————————————————————–+
| Service or Feature access | Turn service or feature ON for users in the group. Always overrides the organizational unit’s setting. | Turn service or feature ON or OFF for users in the organizational unit. |
| User membership | Users from different organizational units can belong to a group. Users can belong to multiple groups. | A user belongs to a single organizational unit.|
| Inheritance | Yes. Groups within a group get access to the service. | Yes. organizational units can inherit or override the parent organizational unit setting. |
Glossary
Organization
When you start with Twake, we have to define only one organization typically takes the form of your organization’s name such as yourbusiness.com. Organization is the top-level organization of your Twake Account.
Organization Unit
To apply different settings to some users or delegate right to manage users settings to a Organizational Manager, place them in a child organization (a Organisation Unit), below the top level Organization. Users in organizations get the settings that you apply to them. So to keep a child organization from inheriting its parent’s settings, apply to the child any settings that are specific to it.
Organizational Hierarchy
Create as many organizational units as you want in a hierarchy. Each child organization inherits settings from its parent, which you can then customize. Changing a setting at a higher level changes the setting for all sub-organizations that inherit that setting.
Twake Account
The Twake Account is the Organizational Admin who can acts as the administrator of your account.
If you have access to an Twake (or admin) account, you can sign in to the Twake Admin console. The Admin console is where administrators manage Twake services for people in an organization.
Twake Console or Twake Admin Console
The Twake Console is where you will manage your entire Twake Account now that it is set up. You can add users, update your company profile, handle billing, and more.
User
To open and use Twake, you must login from a computer, on your phone or tablet. To sign in Twake, go to your login page and enter your Twake account email and password. Once you’re signed in, you can use Twake.
Group or team
You can turn on Twake services or manage specific setting for a group of users rather than an entire organizational unit. This lets you control access for specific users without changing your organizational structure.
For example, turn on the Chat feature for a group of users across your marketing and sales teams. Or set a specific mail quota for a group of users within your IT team. Groups can include any users in your account.
If you have fewer than 50 users, it might be simpler to use only organizational units.
Group or Team Manager
With this privilege, you can access to the Twake Admin Console. Here, you can add users to your Group and manage their services or settings.
Platform Super Administrator
This user is the top level technical administrator account. It is similar to the root account on the Unix system.
Organizational Admin
As administrator of your Twake Account, you are the Organizational Admin. With this privilege, you can access to the Twake Admin Console. Here, you can add users to your account and manage their services. We recommend that you share management of your account with other people you trust by granting them administrator privileges, too. You can make another user a Organizational Admin with complete access to the Twake Admin Console or make another user a Organizational Unit Manager with privileges only on a Organizational Unit.
Organizational Unit Manager
With this privilege, you can access to the Twake Admin Console. Here, you can add users to your Organizational Unit and manage their services or settings.
Domain
To sign your organization up for Twake, you need an internet domain name. This is the unique name that appears after the @ sign in email addresses, and after www. in web addresses. It typically takes the form of your organization’s name and a standard Internet suffix, such as yourbusiness.com. You can use a domain name that you already own. Or you can purchase a domain if you don’t have yet.
Domain alias
If your organization owns multiple internet domains, you can add these to your Twake account at no extra cost. That way, users at all your domains can use your Twake services. For example, a retailer might have domains for different product lines, or a state university might own a domain for each campus.
Multitenancy
The term “software multitenancy” refers to a software architecture in which a single Instance of software runs on a shared infrastructure and serves multiple Tenants.
Instance
Instance is a Twake installation done by using our setup installation guide.
Tenants
A tenant is your dedicated share of a Twake instance - including its data, configuration, user management, tenant individual functionality and non-functional settings. Your Organization is a tenant of the Twake Instance. With the Twake Account, you act as the administrator of your tenant and manage settings and privileges of your Organization.
Role-Based Access Control (RBAC)
Role-based access control (RBAC) restricts Twake Services or Features Access based on a person’s role within an organization and has become one of the main methods for advanced access control. The roles in RBAC generally refer to the levels of access that employees have to the network.
Employees are only allowed to access the information necessary to effectively perform their job duties. Access can be based on several factors, such as authority, responsibility, and job competency.
As a result, lower-level employees usually do not have access to sensitive data if they do not need it to fulfill their responsibilities. This is especially helpful if you have many employees and use third-parties and contractors that make it difficult to closely monitor Twake access. Using RBAC will help in securing your company’s sensitive data and important applications.