An organization corresponds to an enterprise or a tenant. Multiple eSurfing Cloud accounts can join an organization. All operations on DMS for each account are restricted to the organization to which the account belongs, meaning that resources from other organizations are not visible to the user. When you enter DMS with an eSurfing Cloud master account for the first time, the system automatically creates an organization for this account.
One organization has multiple users, similar to multiple employees under one organization. You can become a DMS user either using the eSurfing Cloud master account or sub-account to use DMS features.
An organization can be divided into multiple teams. A team corresponds to a department in the enterprise organizational structure or an R&D project in DevOps. Users and resources in DMS can be associated with the specific team to achieve management domain segmentation. The team functions are as follows:
• An enterprise can divide teams by its organizational structure. Member management and order approval can be completed within the team to achieve self-R&D and efficient collaboration;
• A large organization can manage databases by team to achieve the division of O&M and management responsibilities. Different DBAs are responsible for the O&M of databases in different teams;
• Metadata isolation can be achieved. Ordinary users are restricted from accessing the metadata information of databases not included in the team (such as databases and tables) to enhance the security of metadata access.
Additionally, each organization has a public team by default, which includes all members of the organization. For smaller organizations with fewer database users and instances, you can simply use the default public team for collaboration without additionally creating a team.
DMS supports role management, which mainly contains two categories: system role and team role.
System roles refer to the user's roles within the organization's scope, including: the super administrator, administrators (a system role in the Enterprise Version), and ordinary users. The super administrator is the role that uses the eSurfing Cloud master account to create the organization and is the main body of DMS billing. The super administrator can perform any operation on DMS (such as entering instances, adding users, and more). Administrators are added and designated by the super administrator, and hold most of the permissions as the super administrator, except for switching organization versions, editing organization information, and operating billing-related functions. Ordinary users are added and designated by the super administrator and can only perform restricted operations (such as logging into instances, querying data, and so on). Therefore, visible DMS menu functions vary between different roles.
Team roles refer to the user's roles within the team scope, including team administrators and common members. The super administrator can designate a ordinary user to be the administrator of a specific team; with any permissions of the instances within the team, the team administrator can manage team members and instances within the team, and perform the duties of the instance owner; the common team members can only serve as common developers, and perform daily operation after logging in to the instance.
Database resource is a generic term for all database-related resources including instances, databases, schemata, tables, columns, views, and more. Users can perform operations on database resources, such as entering instances, creating databases, creating views, and so on.
The instance specifically refers to the database instance. Users can enter a database instance in DMS and can log in to the instance using their username and password for data management.
An instance has multiple databases. General data operations are performed under the database, such as table creating and querying.
For databases such as PostgreSQL, there is a schema hierarchy under the database hierarchy. When performing data operations on this type of database, it is generally needed to switch to the schema hierarchy.