Staff Directory Filterable?
- This topic has 4 replies, 4 voices, and was last updated 8 years, 10 months ago by .
Viewing 3 reply threads
Viewing 3 reply threads
- You must be logged in to reply to this topic.
Home › Forums › GovIntranetters › Staff Directory Filterable?
Tagged: staff directory
I’m very interested in this if you get any more info. I’m an outside developer with admin login. I don’t need my clients employees asking who this random person is in their directory.
Are you using a plugin to achieve this? I am using Active Directory Intergration – https://wordpress.org/plugins/active-directory-integration/. Using that I am able to specify Organisation Units (OU) from the active directory. This means as long as our network manager groups staff in these (OU) groups, I can just import the group, excluding the rest of the organisation. Hope this makes sense.
Another more basic tip, is if you remove the firstname and lastname of the users you dont want to see, they will disappear from the Staff Directory. This is helpful if you have generic or guest accounts, messing up your staff directory.
Blanking out first and last name is the only way at present to stop people appearing in the staff directory. However, I’m not sure if your LDAP plugin would reset this when people login again?
Sorry for the late reply. Thanks Tom and Luke: this solution (removing first/last name) works as a temporary measure but yes our LDAP plugin will continue to populate the directory with anyone who logs into our Intranet. What would be awesome is if we could configure the directory to only show users of a certain role designation. That way anyone who is say, a subscriber, would not show and everyone who is an Author or Editor does. We also have some in the Admin role who we would like to not display.
Best,
Nick
Cookie | Duration | Description |
---|---|---|
comment_author_email_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_url_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wordpress_logged_in_[hash] | Indicates when you’re logged in, and who you are, for most interface use. | |
wp-settings-{time}-[UID] | This is used to customize your view of admin interface, and possibly also the main site interface. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | Used to distinguish users. |
_gat | 1 minute | Used to throttle request rate. |
_gid | 24 hours | Used to distinguish users. |