EGSA – What about user permissions in Phase 1?

1. The migration of users from the current EACAT to the new EACAT

• Users that existed in the current EACAT have been migrated to the new EACAT.
• As of release, you can create users only in the current EACAT and there is a continuous migration so that when you query the new EACAT they are already there.
• In future phases, users will be created in the new EACAT, specifically in the Services administration AOC / Users / Create users button. This button is currently not displayed.

2. User permissions in the new EACAT

User permissions are assigned to Administration / Services AOC / Users / Services AOC.

User permissions for EACAT Procedures are 3:

• Basic , everyone has it because it is given automatically when a user is created. When migrating users it was automatically assigned to everyone.
• Entity manager , migrated in a first load. After launch, you can just assign it to the current EACAT and there is continuous integration so that when you look at the new EACAT it's already there.
• Signador , was migrated in a first load, although the lack of signature permission in general across all services in the current EACAT means that continuous integration could not be defined. Therefore, you will need to review the users who have this permission in the new EACAT to ensure that they are the users who should have it.

3. What should you do with new services and new users?

• To the new users, you must assign the roles of each service that corresponds to them in the current EACAT and, at the same time, you must assign the user permissions in the new EACAT (Administration / Services AOC / Users).
• If your organization works with mailboxes and you have already created them, you will add the new users and the new services to the mailboxes that correspond to them. (Administration / EACAT Procedures / Mailboxes).