Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Permission Set Naming convention #8

Open
virtix opened this issue Oct 18, 2016 · 2 comments
Open

Add Permission Set Naming convention #8

virtix opened this issue Oct 18, 2016 · 2 comments

Comments

@virtix
Copy link
Contributor

virtix commented Oct 18, 2016

This is the idea we will add to the docs
[App Short Name] - [Persona or Permission] - [C|R|E|D]

E.g., Mos - Contact Center Agent - CRE or Mos - Delete Contacts - D

Note that for permission sets that are not aligned with a persona, use a present-tense verb to help describe the permission.

As per, @mvogelgesang let's also add Org Wide - [Permission Type] - System [C|R|E|D]

/c @miklane

@mvogelgesang
Copy link

@virtix we have a similar naming convention at GSA. We have some "org wide" permission sets that use the following format:

  • Org Wide - [Permission Type] - System

For example, we have a Lightning permission set which we call "OrgWide - Lightning - System". Another example is "OrgWide - Manage Public List Views - System" which as the name indicates, allows for the management of public list views.

@virtix
Copy link
Contributor Author

virtix commented Dec 5, 2016

@mvogelgesang That's a very good idea. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants