Access Portal

Access Portal

1. Access Request Process:
   • The user logs into the portal and requests access to the resource.
   • The request for this resource is sent to their manager.
   • The manager receives an email about the new request and sees it in the interface.
   • The manager can approve or reject the request:
     • If approved, the request goes to the IT department – which processes the request and after a successful or unsuccessful decision, the user receives an email.
     • If rejected, the request initiator receives an email about the rejection.

2. Access Catalog:
   • The access catalog includes various types of access, for example:
     • Full internet access.
     • Access to a folder with files.
     • Etc.
   • The catalog should have the ability to be edited from the interface.
   • Each access should have a field with a description of that access.

3. Access Package:
   • For example, the "Operator" access package includes:
     • Limited internet access.
     • Access to a folder.

4. Synchronization with Active Directory:
   • Users, their emails, and managers need to be synchronized every 30 minutes (log the synchronization process).
   • There should be a button for manual synchronization in the interface.

5. Portal Authorization: 
   • Access levels (can be tied, for example, to groups in Active Directory):
     • IT with full access.
     • Manager - who can submit and approve requests for their department.
     • View only:
       • Ability to view user accesses.
       • Ability to view who has access to a specific resource.
   • Rights can be combined (for example, manager + view only).
   • Login to the portal with a username/password which can also be taken from the Active Directory controller.

6. Other
7. There should be search + filtering on the portal.
8. Postgres database.
9. Laravel => 10.