Wiki source code of Understanding the role of model owner and company contact
Last modified by Martijn Woudstra on 2022/08/30 11:23
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}}{{container layoutStyle="columns"}}((( | ||
| 2 | |||
| 3 | A crucial part of correctly managing the platform is correctly handling user management within your company and within your integration data models (i.e. projects or buses). In this microlearning, we will zoom in on user management to explain it. Furthermore, we will zoom in on two crucial roles when it comes to user management. These roles are the model owner role and the company contact. | ||
| 4 | |||
| 5 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 6 | |||
| 7 | == 1. Prerequisites == | ||
| 8 | |||
| 9 | * Intermediate knowledge of the eMagiz platform | ||
| 10 | |||
| 11 | == 2. Key concepts == | ||
| 12 | |||
| 13 | This microlearning centers on Understanding the role of model owner and company contact. | ||
| 14 | |||
| 15 | * The key aspects are: | ||
| 16 | ** A model owner grants permissions on integration data model (i.e project) level | ||
| 17 | ** A company contact can add, activate and deactivate users for a specific company | ||
| 18 | ** Both model owners and company contacts can transfer their rights to another portal user | ||
| 19 | ** A model owner is the first point of contact for eMagiz support and eMagiz Expert Services | ||
| 20 | |||
| 21 | == 3. Understanding the role of model owner and company contact == | ||
| 22 | |||
| 23 | A crucial part of correctly managing the platform is correctly handling user management within your company and within your integration data models (i.e. projects or buses). In this microlearning, we will zoom in on user management to explain it. Furthermore, we will zoom in on two crucial roles when it comes to user management. These roles are the model owner role and the company contact. | ||
| 24 | |||
| 25 | * The key aspects are: | ||
| 26 | ** A model owner grants permissions on integration data model (i.e project) level | ||
| 27 | ** A company contact can add, activate and deactivate users for a specific company | ||
| 28 | ** Both model owners and company contacts can transfer their rights to another portal user | ||
| 29 | ** A model owner is the first point of contact for eMagiz support and eMagiz Expert Services | ||
| 30 | |||
| 31 | === 3.1 User management on platform level === | ||
| 32 | |||
| 33 | On the platform level, there are several forms of user management embedded within the portal. In this section we will discuss user access to integration projects, user authorizations to integration projects, the role of the model owner, transferring your model owner role, and the company contact role. | ||
| 34 | |||
| 35 | ==== 3.1.1 Users access to Integration Projects ==== | ||
| 36 | |||
| 37 | Users can be added to Integration projects, which hold all the configurations required to run the different integrations for the TAP environments. Integration projects are connected to organizations in eMagiz to ensure the integration project remains within the limits of the license agreements. Users can be added to integration projects of the organization where the user belongs to. Users can't be added to integration projects of other clients. The model owner and the company contact have the right to add/remove users from an integration project. | ||
| 38 | |||
| 39 | ==== 3.1.2 User authorizations to Integration projects. ==== | ||
| 40 | |||
| 41 | Every integration project has a model owner who can distribute rights across functionalities and environments. In the picture below, one can see the various options available across the Integration Life Cycle (ILM) Phases Capture through Manage. The model owner manages the user permissions and needs to have the MFA authentication level passed before making any changes. | ||
| 42 | |||
| 43 | * In case of Edit permission is granted on an ILM phase, all the sub-options can be configured | ||
| 44 | * View rights mean that all options can be viewed only | ||
| 45 | * In case the user has no Edit or View rights to a certain ILM phase, the phase will not be displayed at all in the eMagiz iPaaS Portal | ||
| 46 | * When you create a new project you will automatically be the model owner of that project | ||
| 47 | * The model owner can transfer his/her rights to another portal user that is active within the context of that project | ||
| 48 | * An audit trail is kept of the changes made in the project permission structure | ||
| 49 | |||
| 50 | [[image:Main.Images.Microlearning.WebHome@intermediate-portal-security-understanding-the-role-of-bus-owner-and-company-contact--access-rights-integration-data-model.png]] | ||
| 51 | |||
| 52 | === 3.2 model owner === | ||
| 53 | |||
| 54 | The model owner is an eMagiz user that is the first point of contact for a certain integration project. By being a model owner you can add/remove users to/from the integration project you are model owner for. Requests of users to get more or fewer rights should pass through you. If you are no longer associated with an integration project you have the option to transfer your role to another active user on that integration project. How to do so is explained in more detail in the following section | ||
| 55 | |||
| 56 | ==== 3.2.1 Change contact ==== | ||
| 57 | |||
| 58 | When you navigate to Administration -> User Management -> Bus permissions you will see a list of integration projects you are the model owner (contact) for. Select the integration project for which you want to transfer your model owner responsibilities and press Change Contact. | ||
| 59 | Select the user that will be the new model owner and press Change contact. | ||
| 60 | |||
| 61 | [[image:Main.Images.Microlearning.WebHome@intermediate-portal-security-understanding-the-role-of-bus-owner-and-company-contact--bus-owner-change-contact.png]] | ||
| 62 | |||
| 63 | === 3.3 Company Contact === | ||
| 64 | |||
| 65 | Every Company that is registered within eMagiz has a so-called company contact. The company contact has two specific functions: | ||
| 66 | |||
| 67 | * Add/Deactive Users within that Company | ||
| 68 | * Backup for the model owner to add/remove a user, and give the appropriate rights, from a specific integration project | ||
| 69 | |||
| 70 | ==== 3.3.1 User management ==== | ||
| 71 | |||
| 72 | When you navigate to Administration -> User Management -> User management you will see a list of companies you are the company contact for. Select the company for which you want to add/edit/deactivate users and based on the action press New, Edit, or Deactivate. | ||
| 73 | Follow the instructions of eMagiz based on the choice you have made to successfully perform the required action. | ||
| 74 | |||
| 75 | ==== 3.3.2 Change contact ==== | ||
| 76 | |||
| 77 | When you navigate to Administration -> User Management -> User management you will see a list of companies you are the contact for. Select the company for which you want to transfer your model owner responsibilities and press Change Contact. Select the user that will be the company contact and press Change contact. | ||
| 78 | |||
| 79 | [[image:Main.Images.Microlearning.WebHome@intermediate-portal-security-understanding-the-role-of-bus-owner-and-company-contact--company-contact-change-contact.png]] | ||
| 80 | |||
| 81 | == 4. Assignment == | ||
| 82 | |||
| 83 | Check out if the model owner for the projects in which you are involved is someone that is still active on the project. | ||
| 84 | |||
| 85 | == 5. Key takeaways == | ||
| 86 | |||
| 87 | * The key aspects are: | ||
| 88 | ** A model owner grants permissions on integration data model (i.e project) level | ||
| 89 | ** A company contact can add, activate and deactivate users for a specific company | ||
| 90 | ** Both model owners and company contacts can transfer their rights to another portal user | ||
| 91 | ** A model owner is the first point of contact for eMagiz support and eMagiz Expert Services | ||
| 92 | |||
| 93 | == 6. Suggested Additional Readings == | ||
| 94 | |||
| 95 | If you are interested in this topic and want more information please check out the [Security Guide](../howto/security-guide.md) | ||
| 96 | |||
| 97 | == 7. Silent demonstration video == | ||
| 98 | |||
| 99 | As this is a more theoretical microlearning we have no video for this. | ||
| 100 | |||
| 101 | )))((({{toc/}}))){{/container}}{{/container}} |