User Roles, hiding certain sections based on user role
- This topic has 2 replies, 2 voices, and was last updated 8 years, 7 months ago by .
Viewing 2 reply threads
Viewing 2 reply threads
- You must be logged in to reply to this topic.
Home › Forums › GovIntranetters › User Roles, hiding certain sections based on user role
Hi there,
I have not yet installed this theme, I have a question before I do.
I’d like to setup my Intranet with Users that have differnent Roles, depending on their Role they can only see certain information (other roles can see more information).
For example: there will be one general user role, they can see most things.
However the Sales team users need access to certain very sensitive information (price lists, suppliers lists etc.) – so I want the only the Sales users to be able to access this information.
I know Worpress has default Roles: Admin, Editor, Contributor, Subsciber – how does this theme meet my requirements?
Any help is much appreciated.
Thanks,
Graham
Hi Graham
WordPress roles mainly concern publication privileges rather than view permissions. You’d need a third-party plugin such as “Membership” to control who can view different sections. Maybe a private wiki or forum would work? Again, you’d need extra plugins to achieve this. There is no default functionality included in the GovIntranet theme to control access for specific user groups.
Hope that helps.
Luke
Hi Luke,
Thanks for taking the time to get back to me. Will take a look at the Membership plugin, your other suggestions are also very helpful.
Cheers,
Graham
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. |