Granting Edit Permissions to Specific Users
Overview
By default, only users with content management roles (Admin, Owner, Learning Designer, Curator) can edit Learnlists. However, Learn Amp allows you to grant edit permissions to specific individual users who wouldn't normally have access—useful when you need a subject matter expert to maintain content without giving them broader administrative rights.
This feature enables collaborative content management while maintaining security and role boundaries.
Functionality Breakdown
How User Editors Work
Delegation: Owners and Admins can designate specific users as "editors" of a Learnlist
Scoped access: Editor permissions apply only to that specific Learnlist, not to all content
Full editing: Editors can modify the Learnlist's content, structure, and settings
No broader permissions: Editors don't gain any other administrative capabilities
What Editors Can Do
Users granted edit permissions can:
Update Learnlist name, description, and settings
Add, remove, and reorder content items
Modify sections and structure
Update visibility and assignment settings
Change scoring and certificate options
What Editors Cannot Do
Even with edit permissions, editors cannot:
Archive or delete the Learnlist (requires Admin/Owner role)
Access other Learnlists they haven't been granted permission for
Manage company-wide settings
Create new Learnlists (unless they have a content management role)
Pre-requisites
Role Requirements
To grant edit permissions:
Owner – Can grant edit permissions to any user
Admin – Can grant edit permissions to any user
Curator (with policy override) – May be able to grant permissions depending on configuration
To receive edit permissions:
Any user in the company can be designated as an editor
Quick Start Guide
Granting Edit Permissions
Navigate to Manage in the sidebar
Select Learnlists
Click on the Learnlist you want to share editing access for
Click Edit to open the Learnlist editor
Scroll to the Edit Permissions section
Check the box to enable additional editors
Search for and select the user(s) you want to grant access to
Click Save
Viewing Who Has Edit Access
Edit the Learnlist
Scroll to the Edit Permissions section
View the list of users who have been granted editor access
Removing Edit Permissions
Edit the Learnlist
Find the Edit Permissions section
Remove the user from the editors list by clicking the remove icon
Save your changes
The user will immediately lose their ability to edit this Learnlist.
FAQs
Q: Will the user be notified when I grant them edit permissions?
No automatic notification is sent. You'll need to inform the user directly that they now have edit access.
Q: Can I grant edit permissions to multiple users?
Yes. You can add as many editors as needed for a single Learnlist.
Q: What happens if I remove someone's edit permissions while they're editing?
They'll be able to finish their current session, but won't be able to access the edit view again after that.
Q: Can editors grant permissions to other users?
No. Only users with Admin, Owner, or (in some configurations) Curator roles can grant edit permissions.
Q: Does this work for other content types?
Yes. The User Editors feature is available for Items, Quizzes, Surveys, Events, and Channels as well as Learnlists.
Q: Will editors see the Learnlist in their Manage area?
Users with editor permissions can access the Learnlist through direct links or by searching in the Manage area if they have list permissions.
Troubleshooting
Issue | Solution |
|---|---|
Can't find Edit Permissions section | Ensure you have Owner or Admin role. The section appears only when you have permission to delegate. |
User can't find the Learnlist | Share a direct link to the Learnlist edit page. They may not see it in default list views. |
Changes not saving | Ensure you click Save after adding editors. Check for any validation errors on the form. |
Editor can't access certain features | Some features (archive, delete) are restricted to Admin/Owner regardless of edit permissions. |
Want to grant permissions to many users | Consider whether those users should have a content management role instead, which would give broader but appropriate access. |