Role Provider Array Bundle Laravel Package

Product Decisions This Supports

• Simplifying Role-Based Access Control (RBAC) for Laravel/PHP apps: Eliminates the need for a database-backed role system when roles are static or infrequently updated, reducing complexity and operational overhead.
• Accelerating MVP development: Ideal for early-stage projects where role management is straightforward (e.g., admin/user tiers) and can be configured via YAML/array instead of a database schema.
• Build vs. Buy: Justifies a "buy" decision for teams lacking time/resources to build a custom role provider, especially if roles are predefined (e.g., SaaS tiers, internal tools).
• Microservices or lightweight APIs: Useful for services where roles are hardcoded (e.g., API gateways with fixed permission sets).
• Legacy system integration: Enables role management in older PHP/Laravel apps without migrating to a database-driven RBAC system.

When to Consider This Package

• Adopt when:

  • Roles are static or rarely modified (e.g., "admin," "editor," "guest").
  • You’re using DCSRoleCoreBundle and need a lightweight role provider.
  • Your team prioritizes configuration over code (roles defined in config/arrays).
  • You’re building a proof-of-concept or prototype where database roles are overkill.
  • Your app has low user volume or roles are scope-limited (e.g., internal dashboards).

• Look elsewhere when:

  • Roles require dynamic assignment (e.g., user-created roles, hierarchical permissions).
  • You need fine-grained permissions (e.g., row-level security, attribute-based access).
  • Your team uses Symfony’s built-in security or Doctrine-based RBAC (e.g., Voters, ACLs).
  • Scalability demands database-backed roles (e.g., SaaS with 10K+ users).
  • You’re integrating with third-party auth systems (OAuth, LDAP) requiring flexible role mapping.

How to Pitch It (Stakeholders)

For Executives: "This package lets us manage user roles via configuration (arrays/YAML) instead of a database, cutting development time by 30% for projects with static roles. Perfect for MVPs or internal tools where simplicity trumps scalability. MIT-licensed and integrates with our existing Laravel stack—no new infrastructure needed."

For Engineers: *"The DCSRoleProviderArrayBundle replaces database-driven RBAC with a lightweight, config-based approach. Key benefits:

• Zero migrations: Roles are defined in config/arrays (e.g., roles.yaml).
• Trait for users: UserRoleArray adds helper methods (e.g., hasRole(), getRoles()) to your User model.
• Symfony/DCSRoleCoreBundle compatibility: Plugs into existing security systems.
• Dev-friendly: Ideal for prototypes or apps where roles are hardcoded (e.g., admin panels). Tradeoff: Not suitable for dynamic roles or high-scale apps—use this for simplicity, not flexibility."*

For Developers: *"To implement:

1. Install via Composer: composer require dcs/role-provider-array-bundle.
2. Configure roles in config/packages/dcs_role_provider_array.yaml (e.g., roles: [admin, user, guest]).
3. Extend your User model with the UserRoleArray trait for role utilities. Pro tip: Pair with DCSRoleCoreBundle for full Symfony security integration. Avoid if you need database-backed roles later—this is a ‘good enough’ solution for now."*