Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Property groups (tabs) already have built in support for access rights. You don't need a UI descriptor for that. You can change the access rights in admin mode or via code, see https://docs.developers.optimizely.com/content-management-system/docs/grouping-content-types-and-properties#apply-access-levels This will limit access both in the on-page-edit and all properties view.
Hello!
Here's a scenario we're trying to accomplish, and we feel like we're close, but missing something.
Scenario:
Goal:
What we've done:
Is there a way to either disable the In-Page editor button when a person of a particular group tries to edit a page they don't have access to?
OR set up the permissions in a away that will let a usergroup only edit fields in a particular property group tab?
I hope this makes sense, thanks!
public override void ModifyMetadata(ExtendedMetadata metadata,IEnumerable<Attribute> attributes) { var cp = PrincipalInfo.CurrentPrincipal; foreach (ExtendedMetadata property in metadata.Properties) { if (property.GroupSettings != null && property.GroupName != null) { string gn = property.GroupName; //TEACHER PREP ADMIN if (!cp.IsInRole("TeacherPrepGroup") && gn == Helpers.EPiServer.Organization.GroupNames.TeacherPrepAdmin) { property.GroupSettings.DisplayUI = false; } } } }