Introduce role-based permissions for dashboard actions

[Lakes41]

Summary

Add a permission model that distinguishes read-only users from admins who can manage passes, members, guild settings, and integration configuration.

Current Behaviour

Management pages are grouped under the same dashboard navigation and do not appear to enforce action-level permissions. Once a user can access the dashboard, there is no fine-grained permission boundary for sensitive actions.

Expected Behaviour

Dashboard actions should be guarded by explicit permissions such as passes:write, members:write, guilds:write, and settings:write.

Suggested Implementation

Define a permission matrix and helper functions such as canManagePasses, canManageMembers, and canEditSettings. Add a mock session model with roles and permissions. Use the helpers to hide or disable actions and protect mutation handlers.

Files or Areas Likely Affected

• apps/dashboard/lib/auth/
• apps/dashboard/lib/permissions.ts
• apps/dashboard/components/DashboardLayout.tsx
• apps/dashboard/app/passes/page.tsx
• apps/dashboard/app/members/page.tsx
• apps/dashboard/app/settings/page.tsx

Acceptance Criteria

• A typed permission model is defined
• Read-only users cannot access write actions
• UI controls are hidden or disabled based on permissions
• Mutation handlers also enforce permissions
• Mock sessions cover owner, admin, moderator, and read-only roles
• Documentation explains the supported roles and permissions

Additional Notes

This should not rely only on UI hiding. Live mode must still depend on backend enforcement for authoritative security.

[Krishna41357]

Hey, I'd like to take this one. I'll define the typed permission model and matrix, build the helper functions like canManagePasses, canManageMembers, and canEditSettings, wire up the mock session model covering owner, admin, moderator, and read-only roles, and use the helpers to both guard UI controls and enforce permissions in mutation handlers. I'll also add docs covering the supported roles and permissions. Happy to get started.

[Arome8240]

Hello, I'm a smart contract and full stack developer, open for contributions. contributed to over 20 project on OnlyDust and Drips , with expertise in Solidity, Cairo, JavaScript, TypeScript, and RUST. I am passionate about building secure and scalable blockchain solutions, and I would love the opportunity to contribute my skills toward solving this issue.

[jaynomyaro]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[grantfox-oss]

🦊 GrantFox — @Krishna41357 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #28)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.