Delegated Roles (Peer-to-Peer Model)
In DBL Next, delegated roles let one organization give specific responsibilities to another. This peer-to-peer model allows you to work with trusted partners while still keeping full control over your organization’s users, roles, content, and agreements.
You can delegate any of these roles to another organization:
- Account Manager
- Content Manager
- License Manager
How Delegation Works
Roles can only be delegated directly to another organization—they can’t be delegated any further. When you delegate a role to another organization, everyone in that organization who already has that same role will automatically get access in your organization. But they can’t pass on that access to other organizations.
Example:
If Third Day Translations gives the Content Manager role to Divine Verse, all existing Content Managers in Divine Verse now have Content Manager access in Third Day Translations.
But if Divine Verse tries to delegate that role to New Bible Society, it won’t work—a delegated role cannot be passed on to another organization. Only the organization that originally holds the role can delegate it.
Conflict Resolution: The Most Permissive Role Wins
If a user has multiple roles from different organizations (whether directly or through delegation), the system will apply the role that gives them the most access.
Example:
Maria has these roles:
- In Third Day Translations: License Manager
- In Divine Verse: Content Manager
By default, she’s not a Content Manager in Third Day Translations.
But if Third Day Translations delegates the Content Manager role to Divine Verse, then Maria, as a Content Manager in Divine Verse, also gets that access in Third Day Translations.
How This Is Different from DBL Classic
In DBL Classic, permissions were inherited through a top-down structure of nested organizations. This often made it hard to understand or manage who had access to what.
DBL Next uses a peer-to-peer model, where each organization directly controls which roles it delegates and to whom. This new approach offers more clarity, better tracking, and fewer surprises—eliminating unintended access caused by complex org nesting.