Modules
Ablebase uses a module system to enable or disable optional features per organization. Admins and owners manage modules from Settings → Features.
Module list
Section titled “Module list”| Module | Optional | Depends on | Description |
|---|---|---|---|
core |
No | — | Authentication, sessions, and the application shell. Always active. |
organizations |
No | core | Organization management and membership. Always active. |
teams |
No | organizations | Team-based member grouping. Always active. |
products |
No | organizations | Products and their configuration. Always active. |
areas |
Yes | products | Subdivisions within a product for scoping issues and risks. |
standards |
Yes | organizations | Custom accessibility standards, requirement groups, and requirements. |
audits |
Yes | products, standards | Accessibility audits with issue linkage and audit scheduling. |
issues |
Yes | products, standards | Issue tracking with requirement mapping and bulk operations. |
risks |
Yes | products | Risk identification, tracking, and materialization into issues. |
views |
Yes | organizations | Saved filters and views for issues and risks. |
integrations |
Yes | products | Connect external platforms (GitHub, Linear) to link repositories and import issues. See Integrations. |
Enabling modules
Section titled “Enabling modules”- Go to Settings → Features.
- Toggle the module on. If the module has dependencies that are not yet enabled, they will be enabled automatically.
Disabling modules
Section titled “Disabling modules”Toggle a module off. Data associated with a disabled module is retained — disabling a module hides the feature but does not delete existing records.
Required modules (core, organizations, teams, products) cannot be disabled.