documenting purpose of AD security groups

Are there any specific best practices you follow when documenting security groups in AD, e.g. what membership of such a group actually permits? Without having to dig through file servers etc a group name on its own is not of much use. So I wondered what type of information you record about each security group, and where you store that information.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The group name and description should be detailed and should convey its purpose.
The other option is to have a naming convention.
The scope of your need might be more elaborate that would be included in your environments documentation, possibly using Visio or similar rendering.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial

I always try to enforce a naming convention, with the end of the name being 'free form' to give more information on purpose etc.

I also try to make extensive notes in the 'notes' section of the group properties in AD, including always:

Date / Time:  Who created or amended / Detailed notes on why the group was created, and I put new notes at the top.

For example:

20171107-2140 (Alan):  Added John Smith per email from Edna Jones (HR Manager) (20171107 - 1054 - Please add John to HR group.msg)

20170131-1345 (Alan):  Group created to give access to //ServerName/ShareName/HR folder

I also file emails in folders (network drives, as well as in Exchange), hence the reference to an msg file, but that could easily be a scan of a hardcopy form, or a fax (rare these days), or a voice recording.

I have been very grateful to my past self numerous times for the notes I created at the time!

Pete LongTechnical ConsultantCommented:
I name all mine

GP-U-{sensible name}
GP-G-{sensible name}
GP-D-{sensible name}

For universal - global and domain local and I put something descriptive in the 'description' field, as that's whats visible when you browse AD

i.e. 'Group for read only access to folder xyzy created xx/xx/xx by PeteLong'

Also I don't use spaces so things are a bit easier If I need to script anything!

Shaun VermaakTechnical SpecialistCommented:
Reduce groups by using role groups and delegation groups
Good advice offered
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.