1. Training: dates, presentation and others

1. Will you send us the course presentation by email or share it somewhere?

We will share the presentation on Campus > Training type > Webinar > new EACAT

Remember that a certificate of completion is not issued for webinar sessions.

2. Will you video record the training so we can review it later?

Yes. You can find it on our YouTube channel:

You also have training material available: videos on campus and FAQs on the support portal.

3. Is any training planned for the new EACAT for service providers?

Yes, there are training courses planned for service providers, but at this stage they will only be held for the entity's managers.

4. Have you summoned the managers of the municipal companies?

Yes, we have summoned all the managers of EACAT. However, we used the Mailchimp email tool, and some emails may have been marked as spam (SPAM).

You can find all the information in the news on the AOC Consortium blog:

5. What happens if you don't have user permissions and access to services (mailboxes) configured in September?

In principle, it is important to have both user permissions and mailboxes configured. Have tools that will facilitate user and service management tasks to ensure that everything is ready on time.

2. Access to the new EACAT

1. What is the link to access the new EACAT?

The web address of the new EACAT is: https://eacat3-cl.aoc.cat/

Find more information in AE – What is the web address of the new EACAT?

2. What can we do if it tells us that the certificate is invalid?

First, check if you can access the current EACAT with the same certificate. If you can access the current one but not the new one, it is recommended to open an incident with our User Support Center (CAU). Provide the exact time and the NIF related to your certificate for better technical assistance.

Find more information in AE - What can you do if you have forgotten your password?

3. Navigation bar

1. How can we choose the entity in which we want to work?

There are users who work in several entities that are members of EACAT. You can select the entity you want to work with in the upper right part of the navigation bar.

To improve your browsing experience, you can select the entity you want to appear by default when accessing EACAT, by going to: Personal space > General > Preferences > Default entity

You will find more information in the FAQ How can you change the default entity when you access EACAT

4. Manager's space | Services AOC

1. Have users from the current EACAT been migrated to the new one?

Existing users in the current EACAT have been automatically migrated to the new EACAT.

From launch, new users must be created exclusively in the current EACAT, as there is a continuous migration process that ensures their availability in the new EACAT.

In future phases, user creation will be done directly in the new EACAT, specifically in Service Administration AOC > Users > Create users. Currently, this button is not available.

Find more information in AE - What will I do in the new EACAT and what will I do in the current version?

2. What is the difference between inactivating a user and deleting them? When should we do one thing and when the other?

Deactivating a user and deleting them are two different actions, and are applied in different situations:

  • Deactivating a user is done when they temporarily do not need to access the system, either due to temporary absence or other reasons that prevent access to EACAT for a certain period.
  • Deleting a user is done when they no longer work at the entity or there are reasons for the user to be permanently removed from EACAT at that entity.

3. How do we deactivate a user?

Currently, you need to go to the current EACAT and deactivate the user. Thanks to the seamless integration between the two platforms, the user will automatically switch to an inactive status in the new EACAT.

When only the new EACAT is used, we will be able to:

  • Deactivate the user, if we do not want them to work in any AOC service.
  • Remove all permissions from EACAT Procedures, if we want it to work in the rest of the AOC services.

4. When we talk about permissions, what exactly are we referring to?

The permissions in the new EACAT correspond to the roles of the current EACAT: basic, entity manager and signatory.

On the other hand, we have user access to inter-administrative processing services, which in the new EACAT corresponds to mailboxes.

5. Where can we manage user permissions in the new EACAT?

You can assign permissions to users from Administration Services AOC Users select the user Services AOC.

Currently, this management must be done in both the current and the new EACAT.

6. Will user permissions for AOC services be migrated?

The permits for the AOC services, except for those for EACAT Procedures, will be migrated to the new EACAT at a later stage. They are not currently migrated.

When the migration is done, you can assign permissions in Administration settings >   Services AOC > account_circle Users > Services AOC

In this phase, you can manage the permissions of the EACAT Procedures service (basic, entity manager and signatory).

7. How should we manage permissions for the AOC services: SIR, e-Valisa, CESICAT, Via Oberta, eNotum and others?

During this phase, permissions for the AOC services are not managed in the new EACAT .

At a later stage, all existing permissions will be migrated to the new EACAT. From this point on, you can manage them in Services Administration AOC > Users > Select user > Services AOC

8. Will EACAT Procedures user permissions be migrated?

The system for providing access to inter-administrative processing services has undergone changes; they are no longer assigned individually for each service, but are now managed through a new system, known as mailboxes.

9. If we manage more than one entity, will we have to assign permissions to users in all entities?

Yes, each entity will need to manage user permissions and user access to inter-administrative processing services. You have tools that will make this task easier, such as mailboxes and the function of exporting/importing services and users within a created mailbox.

10. Where do we register new managers?

If you assign a user the entity manager permission in the current EACAT, this permission will automatically be updated in the new EACAT. However, the same does not happen the other way around. Therefore, it is recommended to assign this permission to both platforms.

In the new EACAT, you can assign this permission to Administration Services AOC Users select the user Services AOC

11. If we have users without any permission to any service in the current EACAT, do they appear in the new EACAT with basic permission? Will we have to remove their permission one by one?

Yes, these users will appear with basic permission in the new EACAT but, if you do not add them to any mailbox, they will not see anything in the Processing Space.

12. Can a user with basic permission edit a procedure of an inter-administrative processing service?

Yes, although it will be different depending on whether your entity has the mailbox system activated or not:

  • Without mailboxes : nothing additional needs to be done, since all users see all procedures, therefore, the user will be able to edit them.
  • With mailboxes : the user will be able to edit the procedure as long as the service is assigned to the same mailbox as the user.

13. What should we do with new services and new users?

You will assign the new users the corresponding roles for each service in the current EACAT and, at the same time, the user permissions in the new EACAT (Administration / Services AOC / Users).

If your entity uses mailboxes and you have already created them, you will have to add the new users and new services to the corresponding mailboxes (Administration / EACAT Procedures / Mailboxes).

In this initial phase, this task must be performed on both the current EACAT and the new EACAT.

14. How does the signatory permission work in the new EACAT?

The signer permission in the new EACAT is assigned to the user and applies to all services. Therefore, a user with the signing permission in EACAT Trámits will be able to sign in all inter-administrative processing services.

Any user with signer permission can also edit a service procedure.

15. Can a user have signing permission for some services and not for others, within EACAT Procedures?

No, signing permission is assigned to the user and applies to all inter-administrative processing services.

However, when carrying out a procedure, there is the possibility of choosing and recommending a preferred signatory. Find more information in EP - What does the option “Check the existence of a preferred signatory” imply?

16. Will the Check-in and Check-out service become a AOC service?

It will soon become a AOC service and what will be done is to associate users who currently have the check-in and check-out permission with this service. We will communicate when this change is made.

5. Manager's space | EACAT Procedures

1. Is it possible that we don't see the Services section of EACAT Procedures and neither the Mailboxes section?

Access the Administration tab and select EACAT Procedures.

5.1. General

2. Does everyone have to have mailboxes activated in the Manager's Space?

Yes, except for entities that expressly responded that they did not want to organize themselves through the mailbox system in the email we sent you on this subject. To verify this, you can go to Administration EACAT General Procedures and activate the Use mailboxes in the entity switch.

5.2. Users

3. Can we obtain a list with the relationship between users and services in the current EACAT?

Yes, we have created a list that you will find in the current EACAT. You can download it from Users Configuration Users/Services/Promoter list

This list is useful for organizing mailboxes in the new EACAT, if you have chosen this system for your entity.

4. Can we know which users have the same permissions in the new EACAT?

Yes, you can find out which users have certain permissions through a list that you can download by applying a series of filters:

  • Status (All, Active, Inactive)
  • Permission (basic, entity manager, lender and signatory)
  • No basic permission

For example, to find out which users have permission to Signador:

  1. Select the Signador option from the Permission filter
  2. Press the ... icon and select Export users.
  3. A list of users who have the Signador permission will be downloaded.

This list will provide you with a clear view of the permissions assigned to users in the new EACAT. Find more information at https://suport-eacat.aoc.cat/hc/articles/18698499601181-EGT-Com-t-exportes-la-llista-de-serveis-de-la-teva-entitat-d-EACAT-Tr%C3%A0mits

5. Are members of the local corporation in office (mayor, secretary, auditor) activated by default in all services?

Local corporation members do not have all services automatically activated by default. This activation depends on the mailbox configuration:

    • If you do not have mailboxes activated: all users of the entity have access and can work with all services, without the need for additional configuration.
    • If you have mailboxes enabled: users who need access to all services can be added to the global mailbox. This mailbox is created by default with all existing and future services when the mailbox system is activated and therefore any user added to this mailbox will have access to their services.

You will find more information about how to organize mailboxes in your organization and the global mailbox at:

6. Will user access to services and the roles assigned to them be migrated to the current EACAT? How will this be managed?

User access to services is NOT automatically migrated to the new EACAT. It is necessary to review and adjust user permissions, especially after a previous migration before 06/26/2024, as some permissions may not match.

User permissions are managed in Administration Services AOC Users select a user Services AOC.

Details to consider

  • If you don't have mailboxes enabled: no action is necessary, but all users will see all services without restrictions.
  • If you have mailboxes enabled: You must manually add services and users to each mailbox. You can import services or users to a specific mailbox. Mailboxes are designed so that only the users in them can access the assigned services.

Find more related information at:

5.3. Services

7. Is generic delivery just another service?

Yes.

8. How can we make generic submissions not visible to everyone?

Within the mailbox, organizational units delimit the visible generic requests. If you do not add an organizational unit (OU), all users of the mailbox can see the generic requests (PGEN) that arrive at your entity. However, when you add the OU, they will only see the PGEN that have the OU selected as the source or destination.

This functionality is not yet enabled in the new EACAT.

9. When the generic request is integrated with the MUX and with the entity's case manager, does it make sense that generic submissions are not received by everyone?

No, but there are many entities that do not have integration with their case manager.

10. Will users who are currently assigned the role of Entry/Exit Registration be migrated directly to the new REGISTRATION service?

The Check-in and Check-out Register will soon become a AOC service. When this happens, users who currently have the check-in and check-out role will be associated with this new AOC service. We will let you know when this change is made.

11. How do we know what each procedure is for? Are there some that we don't know what they are for and, therefore, we can't decide which mailbox they should go to?

In Services you will find a complete list of all available services with detailed information about each procedure they include. You can access this information by pressing the eye icon, which will allow you to view the specific details of each procedure.

12. Why do we create a Discarded services mailbox?

The Discarded services mailbox is a recommended option for the efficient management of procedures in your entity, as explained in the EGT FAQ - How do you organize your entity into mailboxes?

In this mailbox, the services that your entity decides not to manage are assigned. To better understand the processing volume of each service, we have a list that shows your entity's activity in the last 7 years until June 24, 2024, accessible in Services icon ... Export processing volume

This mailbox is particularly useful for entities such as universities that do not use most of the available procedures.

Find more information in EGT – How do you export the list of services in your entity within EACAT Procedures?

13. Where can we find the list with the processing volume? And what is it used for?

Access Services icon ... Export processing volume and download the CSV file with the list of services and the processing volume of your entity during the last 7 years until June 24, 2024. The file includes the following fields:

  • Service_name: service name.
  • Service_code: service identification code.
  • Processing_volume: Number of processing operations.
  • Recipient: name of the entity receiving the service.
  • Provider: Name of the entity providing the service.
  • Generic_service

By exploiting the data in this list, you can identify the services that you have not processed. These services can be assigned directly to the Discarded mailbox, depending on the recommended use case. This allows you to significantly reduce the number of services that you need to distribute between mailboxes.

Find more information at:

14. In the new eacat, the AOC e-board service appears to me as the AOC service and also as the inter-administrative processing service. Is there any difference?

Yes, they are different things: one is the inter-administrative processing service with the corresponding procedure and the other is the link to the AOC e-TAULER service.

The e-TAULER Manual explains why an inter-administrative processing service was created to send external edicts.

15. Is there anything that needs to be done with the generic inter-administrative processing services of the classic EACAT? We are referring to: generic submissions; Notification - Electronic communication of the Generalitat of Catalonia and its public sector; and Generalitat Communications - Third-party files

In EACAT Classic, they must continue to be managed by users who have the check-in and check-out role.

In the new EACAT they must be assigned to a mailbox. As a good practice, we advise you to create a Generic mailbox where the generic services and the users who have to manage them would go.

5.4. Mailboxes

16. If we don't use mailboxes, then everyone will be able to sign everything?

It is important to note the difference between user permissions (basic, manager and signer) and user access to services (mailboxes). User permissions are assigned individually to each user and determine what actions they can perform with respect to the services. This means that, within the same mailbox, only users with signing permission will be able to sign.

User permissions are assigned to Administration Services AOC Users select a user Services AOC".

User access to administrative processing services is managed through mailboxes. To add users and assign specific services to mailboxes, go to Administration EACAT Procedures Mailboxes

17. In a small town hall where everyone has access to all procedures, how can we restrict the view to the procedures sent and received?

Only through mailboxes.

18. In small municipalities with only 3 users in EACAT, does it make sense to use mailboxes? Are new services assigned automatically?

In this case, we recommend disabling mailboxes and all users will see all services without the need to add anything. New services will be assigned automatically and will be visible to all users of the entity.

If you want to deactivate mailboxes, access Administration EACAT General Procedures and activate the Use mailboxes in the entity switch.

19. What should we do if we have opted for the mailbox system in our entity?

We have proposed a hybrid mailbox organization system that is mainly based on distributing services into thematic and sub-thematic mailboxes. In addition, we have created other mailboxes to facilitate management:

  • Generics
  • Discarded
  • Global, created by default with all services, current and future, where we will add those users who need to see everything, such as the secretary, the auditor and the secretary-auditor.

Find more information at:

20. When we activate mailboxes, do we have the global mailbox and 40 specific mailboxes?

Yes. The global mailbox is created automatically when mailboxes are activated in our entity. And we can also create 40 more mailboxes.

You will find more information at:

21. Can we create the mailbox system according to an organization based on the different entities providing the service?

Yes, although it requires good planning to determine the best option for your entity.

From the Consortium, we have provided you with a use case as a starting point that can help you. Although it is not necessary to copy it exactly, it will surely help you reuse some ideas and adapt them to your needs.

22. The Mailboxes section may not appear? Can we choose whether to activate them?

You should see the Mailboxes section. If you don't, you may be in the AOC Services administration instead of EACAT Procedures. Go to Administration and select EACAT Procedures. You should see the mailbox section, even if it is not yet activated. If you do not have the mailbox section activated, you will see the following message:

Mailboxes
Mailboxes are not activated in the entity. Therefore, all users have access to all of the entity's services.

If you want to restrict users' access to certain services, you must activate mailboxes from the General section.

If they don't appear, you can activate them by going to the General section and activating the Use mailboxes in the entity switch.

23. Can the same service be in more than one mailbox?

Yes.

24. Can we assign procedures for a service to different mailboxes?

No, the services are a set of procedures that cannot be separated. They work as a whole. However, you can assign the same service to different mailboxes according to the management needs of your entity.

25. Can a user belong to more than one mailbox?

Yes.

26. When you add a user to a mailbox, are the services already assigned to them automatically incorporated?

No, the services a user is currently assigned are not automatically included when you add them to a mailbox. You must manage mailboxes manually, adding services and users according to the needs of each mailbox.

We propose a use case in the EGT FAQ - How do you organize your entity into mailboxes?

27. Why is the limit 40 mailboxes? Will you expand it in the future?

It will be expanded if necessary, although each case will be previously studied.

28. Do you plan to integrate mailboxes with a file manager such as Audifilm?

No, the mailbox concept is only for the management of EACAT procedures, but you can send an email to Raimon Nualart or José Luís Pastor and we will provide you with more information.

5.5. Organizational units

29. How do organizational units work?

Organizational units do not apply at the moment because they do not yet work in the new EACAT. EGT - What do you manage in the Organizational Units section of EACAT Procedures?

30. The generic delivery groups in the current EACAT work for received deliveries but not for sent ones. Is it expected that in the new EACAT it will also work for sent ones?

Yes, the generic transmission can select the organizational unit (the user group in the current EACAT) both in origin and destination, a new functionality in the new EACAT.

Within the mailbox, the organizational unit (OU) delimits the generic requests that can be seen. If you do not assign an OU to the mailbox, all users of that mailbox will have visibility over all PGENs that arrive at the entity. However, if you assign a specific OU, they will only see PGENs that have the selected OU as the source or destination.

This functionality is not yet active in the new EACAT.

6. Processing

1. Will we be able to draft web forms? That is, will I be able to save them so that one user can fill them out and another can sign them later?

Yes, they will be saved in the Processing Space as a draft.