permissions field from your JWT token on every page request and uses it to:
- Show or hide menu items based on role
- Display the appropriate header for your account
- Filter post content visibility for role-restricted articles
- Toggle administrative UI elements in the WordPress admin
Access by role
- Logged out
- Refugee user (blog)
- NGO admin (org_admin)
When you visit the blog without logging in, you see the public view:
- Public articles and resources available to all visitors
- A login prompt in the page header
- The standard public navigation menu
Menu item visibility
Navigation menus on the blog are configured to show items selectively based on login status and role. A menu item can be set to display for:- All visitors — shown to everyone, including logged-out users
- Logged-in users — shown to any authenticated user regardless of role
- Specific roles — shown only to
blogusers or only toorg_adminusers
Changing your role
Roles are assigned by WeCareRemote administrators when your account is created or updated. You cannot change your own role. If you need a different level of access — for example, if you are an NGO staff member who needsorg_admin access — contact WeCareRemote support to request a role change.
Your permissions are encoded in your JWT token at login. Every time the blog verifies your session, it reads the
permissions field from the token to determine what you can access. You can view your current permissions using the [angular_user_info] shortcode on any blog page.Configuring role-specific menus (for admins)
If you are anorg_admin configuring menus in WordPress:
Set visibility
Use the WeCareRemote visibility selector to choose who sees the item — everyone, logged-in users, only
blog users, or only org_admin users.Common patterns
- Public landing pages with
[wcr_login_form]embedded for easy sign-in. - Resource libraries visible only to logged-in users, so anonymous visitors do not consume them.
- Internal NGO playbooks restricted to
org_adminusers for staff-only documentation. - Refugee-only support guides restricted to the
blogrole, so the content stays focused on the audience it is written for.