Application navigation
The Gredit interface is organized through a sidebar menu that provides access to all system modules. The menu structure reflects the platform's operational logic, dividing functionalities into two main categories.
Operational modules
Day-to-day process and case management.
| Module | Description |
|---|---|
| Cases | Management of detected findings |
| Requests | Registration of change requests |
| Scripts | Definition and management of programmed logic |
| Jobs | Configuration of scheduled tasks |
| Rules | Execution of actions on findings |
Configuration modules
System administration and environment setup.
| Module | Description |
|---|---|
| Roles | Definition of access profiles |
| Users | User account management |
| Access logs | System access auditing |
| Accounts | Logical segmentation of information into tenants |
| Tags | Definition of classification categories |
| Descriptors | Metadata for information classification |
| Processes | Real-time system monitoring |
| Servers | Execution server configuration |
| Databases | Database connection configuration |
| LDAP | Directory service integration |
| SAML | Federated identity provider integration |
| DRIVE | Cloud storage integration |
| PDF Templates | Report template design |
| Integrations | REST API and AWS connectivity |
Navigation logic
Users access the operational modules to carry out daily tasks: creating and managing cases, reviewing requests, running scripts and jobs, and defining rules.
The configuration modules are used to set up the initial environment and make administrative adjustments. Most operational users will primarily access the operational modules, while system administrators will also use the configuration modules.