Table of Contents
Users have permission to view and update resources based on certain rules.
Generally, these rules are defined in the Permissions class, which provides methods to retrieve data based on the current user's permissions.
An additional layer is provided by the gem CanCanCan, which has rules defined in the Ability class. Many of these rules use Permissions or other scopes to check access.
The ResourceController automatically checks for permission on each action, and can be called directly for a class or instance, for example:
can?(:admin, EnterpriseFee) && can?(:manage_enterprise_fees, enterprise)
See the CanCanCan readme for more details.
See also
Permissions are described in the user guide:
Home
Development environment setup
- Pipeline development process
- Bug severity
- Feature template (epic)
- Internationalisation (i18n)
- Dependency updates
Development
- Developer Guidelines
- The process of review, test, merge and deploy
- Making a great commit
- Making a great pull request
- Code Conventions
- Database migrations
- Testing and Rspec Tips
- Testing GitHub Actions Locally with act
- Automated Testing Gotchas
- Rubocop
- Angular and OFN
- Feature toggles
- Stimulus and Turbo
Testing
- Testing process
- OFN Testing Documentation (Handbooks)
- Continuous Integration
- Parallelized test suite with knapsack
- Karma
Releasing
Specific features
Data and APIs
- API documentation
- Authentication
- Integration & API
- Data migration
- Data model diagram (ERD)
- Stripe
- DFC Guide
Instance-specific configuration
External services
Design
- Design styleguide: colors and shadows
- Design styleguide: fonts and text styles
- Design styleguide: size and spacing
- Design styleguide: icons
- Design styleguide: links and buttons
- Design styleguide: navigation and menus
- Design styleguide: tables
- Email templates
- Design tools
Product