go-admingo-admin
  • Guide
  • Development
    • Advanced
    • Commands
  • Advanced
  • Help
  • GitHub
  • Changelog
⌘ K
Standard Practice
Standard Module Development
Backend Basics
Backend Directory Structure
Backend Config File
Starting the Backend
Frontend Basics
Frontend Directory Structure
Frontend Config File
Starting the Frontend
Development Patterns
Actions Pattern
Hand-Written Pattern
First API Endpoint
Layered Development
API Layer
Service Layer
DTO Definitions
Model Definitions
Router Registration
Multi-Environment Config
Database Table Conventions
Data Permissions
Response Format
Code Generation
Pre-Generation Setup
Generating Business Code
One-Click Menu Generation
Binding APIs to the Menu
Configuring Role Permissions
Verifying the Feature
Generating Code with an LLM
Advanced Capabilities
Runtime Core API
Authentication & Authorization
Logging
Request Tracing
Cache
Queue
File Upload
Rate Limiting
Scheduled Jobs
Air Hot Reload
Swagger Docs
Code Generation Tool
Last updated:
Open-source MIT Licensed | Copyright © 2020-present
Powered by go-admin-team

TABLE OF CONTENTS

‌
‌
‌
‌

Configuring Role Permissions

Go to Role Management and open the role list.

Pick the role to grant access to, click Edit, check the menu and API you just generated, and save.

Refresh the page, and the menu you just authorized will appear in the sidebar.

INFO

Signing in as the super admin won't tell you whether the authorization worked — the admin role bypasses Casbin entirely and can call any API (see Authentication & Authorization). Whether a menu appears in the sidebar depends on this role-to-menu assignment, which is a separate mechanism from API-level permission checks — even the super admin needs this step for the menu to show up.

To verify that permission enforcement itself actually works, test with a non-super-admin account.

WARNING

Where to get help:

If anything in this guide is unclear, please open an issue.