Skip to main content
WeCareRemote assigns every account a role that determines what you can see and do on the platform. Your role is set when your account is created and is encoded in your JWT token on every login. There are two roles: blog for refugee users and org_admin for NGO administrators. Roles are intentionally simple. WeCareRemote optimises for clarity over granularity — the two roles map cleanly to the two real-world audiences the platform serves, and every feature is reachable from one or the other without requiring complex permission matrices.
Who this is: Refugees accessing services, information, and support through WeCareRemote.With the blog role you can:
  • Chat with the AI assistant to get information and request support
  • Read blog posts and resources published on the platform
  • Join video meetings with NGO staff
  • View content and navigation tailored to your logged-in state
Blog access: Standard content is available to you after login. The page header and navigation update automatically once you are signed in, showing options relevant to refugee users.

​
Checking your role

Your role is returned in the JWT token verification response under the permissions array. To see your current role, verify your token at POST https://getme.global/api/v1/wordpress_auth/verify_jwt_token and inspect the response: 
{
  "permissions": ["org_admin"]
}
A refugee user account returns: 
{
  "permissions": ["blog"]
}
For full details on verifying your token, see JWT tokens.

​
Role-based content

The blog header and navigation menus adapt automatically based on your login state and role. You do not need to configure anything — the platform detects your role from your token and adjusts what you see.
StateWhat you see
Logged outPublic header with general navigation
Logged in as blogRefugee user header with service and chat links
Logged in as org_adminAdmin header with content management and admin links

​
Permission matrix

Actionblog (refugee)org_admin (NGO)
Read public blog content✅✅
Read role-restricted blog content✅✅
Chat with the AI assistant✅✅
Join a video meeting✅✅
Start a video meeting recording❌✅
List meeting recordings via API❌✅
Publish or edit blog posts❌✅
Access WordPress admin❌✅
Manage menus and role visibility❌✅
If you receive a 403 Forbidden response from the API or a “permission denied” message in the platform UI, the most likely cause is that your role does not include that action.
Your role is assigned when your account is created. If you need your role changed — for example, to gain org_admin access — contact WeCareRemote support at wcr.is/home.