Home
Removing a person's or a group's access
If one or more people leave the company, you can prevent them from being able to access the features by removing that user or group from the LDAP
The LDAP defines who can access Lotus Connections. After removing the person's user ID and credential information from the LDAP directory, synchronize the change with each feature. See Synchronizing IDs between LDAP and the feature databases.
Do not attempt to delete all of the data or content created by the person.
To manage data left behind by a person or group that has left the company, complete the following step: These are optional procedures.
- If the person who left was the sole owner of an activity that other people still use, add one or more additional owners to the activity, so that it can continue to be managed by someone. To add owners to an activity, perform the steps in this procedure: Manage member access to activities. Use the setOwnerAccess command in the list of options in Step 6 to add one or more people to the owner role in the member list of the activity.
- To edit or delete a blog owned by a specific person, complete the steps in this procedure: Administer Blogs users
- To remove bookmarks created by a specific person from the Bookmarks feature, complete the steps in the this procedure: Delete unnecessary links. See the deleteLinkByPerson command options.
- To remove a person's profile, complete the steps in this procedure: Synchronize LDAP changes with Profiles.
- To remove files owned by a specific person, complete the steps in this procedure: Delete user files from the system
- If the person who left was the sole owner of a wiki that other people still use, add one or more additional owners to the wiki, so that it can continue to be managed by someone. To add owners to a wiki, perform the steps in this procedure: How do I add and remove wiki members?
Administer all Lotus Connections features
Related tasks
Synchronize IDs between LDAP and the feature databases