0 votes

Hi,

I'm interested in understanding the easiest/best way to allow users to be able to manage their own personal membership to public distribution lists. Can we put these distribution groups in a specific OU, such that all employees can join or leave these specific distribution groups at will? Ideally they should be able to see all the distributions in said OU, determine whether they are a member or not, and add or remove themselves- but not add/remove other people (unless they are of an elevated permission).

Thanks!

by (80 points)

1 Answer

0 votes
by (18.0k points)

Hello,

Yes, it is possible to implement your scenario using Adaxes.

  1. Define two Custom Commands for adding and removing users to/from groups. The commands will add/remove the account of the initiator to/from the selected distribution list.
    When creating Custom Commands, on the 2nd step of the wizard, select the Group object type.

    On the 3rd step of the wizard, click the Add Action link and select the Run a program or PowerShell script action.

    Use the following scripts to add/remove the initiator to/from groups:
    Add to Group

     $Context.TargetObject.Add("Adaxes://%adm-InitiatorDN%")
    

    Remove from Group

     $Context.TargetObject.Remove("Adaxes://%adm-InitiatorDN%")
    
  2. Grant permissions to users to execute the two Custom Commands for the groups located in a specific OU. For more details, see Grant Rights to Execute Custom Commands.

  3. Configure the Home Page of the Web Interface. For more details, see Configure Home Page Actions.

    Define a Home Page action to execute the Add to Distribution List command you created on the first step.

    • On the Target Object Selection step, enable the Allow selecting only AD objects located under a specific OU or container option, and specify the DN (Distinguished Name) of the OU where groups are located. To get the DN of an AD object, right click it in Administration Console, open the submenu of the Copy item, and select Copy DN.
    • Enable the Allow selecting only AD objects that match the specific LDAP filter option and enter the following LDAP filter: (!(member=%adm-InitiatorDN%))

Define a Home Page action to execute the Remove from Distribution List command you created on the first step. Apply the same options for the action, and specify the following LDAP filter: (member=%adm-InitiatorDN%)

Define a Home page action to allow users to view the groups they are member of.

  • Select the View User action and click Next.
  • On the Object Selection step, select the Always view properties of the currently logged on user option.
  • On the View Customization step, enable the Use customized view option and click Customize View.
  • Customize the view to display only the Member Of section. For details, see Customize Forms for User Creation and Editing.

At the end, the Home page of the Web Interface will look like this:

Related questions

0 votes
0 answers

Good Afternoon, I'm looking for some clarification on what security settings I would need to apply to the Self-Service Users to allow them to update both their own ... accounts they have full access to. Please let me know if this requires more clarification.

asked Jul 22, 2021 by jtop (700 points)
0 votes
1 answer

We need to know specifically for self service password management what level of access in AD do I specifically need.

asked May 9 by justinspring (20 points)
0 votes
1 answer

We have a rule setup that when a user requests membership into a group it will email approvers of the group for approval. I would like to create a report that sends out a list of ALL approvers for every group we have approvals setup for.

asked Dec 18, 2023 by jujones79 (20 points)
0 votes
1 answer

Hey, any ideas on this: I like to activate an out of office notice on a specific account (On-Prem-Exchange if this matters) and deactivate it again. But this should ... or public holidays. Thanks in advance and please let me know if you need more information.

asked Oct 5, 2023 by roppiffm (130 points)
0 votes
1 answer

I think this started happening back in August when we updated to the current version (3.13.18.106.0). We are not sure though because this only affects the web page ... We would prefer not to allow access through a firewall for this. Screenshot of the error:

asked Nov 23, 2020 by mark.it.admin (2.3k points)
3,548 questions
3,239 answers
8,232 comments
547,814 users