Hi!
I’m trying to understand why workspace membership endpoint is returning is_admin = False for a user who is an Admin in the organization.
Here is the API response:
{
"data": {
"gid": "1203231768670529",
"user": {
"gid": "1203231768666896",
"name": "User2 Lumos",
"resource_type": "user"
},
"resource_type": "workspace_membership",
"user_task_list": {
"gid": "1203231768673883",
"resource_type": "user_task_list",
"name": "My Tasks in 1200898892968951.5saz7w.asanatest1.us"
},
"workspace": {
"gid": "1203231852382558",
"name": "1200898892968951.5saz7w.asanatest1.us",
"resource_type": "workspace"
},
"is_active": true,
"is_admin": false,
"is_guest": false,
"vacation_dates": null,
"created_at": "2022-10-24T22:52:26.150Z"
}
}
And my Admin dashboard:
The field description is pretty generic Reflects if this user is an admin of the workspace., but I believe being an admin or a super admin should make this field true, as said here.
Why is_admin is false in this scenario? Shouldn’t it be true?
We are also facing the same issue with is_admin attribute returning false for admin accounts.
But, for some other accounts this seems to be working fine.
Can you please let us know if there a fix for this issue.
Thank!
Hi @anon16883347,
Apologies for the late reply, we missed this discussion. As the documentation states the is_admin property is a boolean value on the workspace_membership object that represents if a workspace member is the admin of the domain (“Reflects if this user is an admin of the workspace.”).
Based on your response and screenshot the value for "is_admin": false, is correct. This is because the user in this case is:
"user": {
"gid": "1203231768666896",
"name": "User2 Lumos",
"resource_type": "user"
},
If you take a look at your screen shot, notice that the user User2 Lumos is just a Member and not an Admin or Super Admin:
This is why the is_admin property is false
@Memory_Engineering_T can you provide screenshots + responses to help us further understand your issue? If it has sensitive information in it please send me a direct message.
Thanks for the reply @John_Vu .
Here is the screenshot of our workspace admin console:
And this is what we are getting back from API:
{:gid=>"1207832312681883",
:user=>{:gid=>"1207832329565556", :name=>"Memory Engineering Team", :resource_type=>"user"},
:resource_type=>"workspace_membership",
:user_task_list=>{:gid=>"1207832312681897", :resource_type=>"user_task_list", :name=>"My Tasks in Timely"},
:workspace=>{:gid=>"457644112916595", :name=>"Timely", :resource_type=>"workspace"},
:is_active=>true,
:is_admin=>false,
:is_guest=>false,
:vacation_dates=>nil,
:created_at=>"2024-07-17T12:15:02.380Z"}
Hi @Memory_Engineering_T ,
Thank you for sharing that info. That does look strange. One possibility I could think of is that the user account you shared could be a part of multiple workspaces and they are only admin of the workspace you shared in your screenshot and not an admin of the workspace in the response.
On closer inspection, it seems like the workspace “Timely” from your screenshot matches the workspace “Timely” from your response (I am just basing this off the naming). This user could probably still be a part of two workspaces named “Timely”.
I’ll bring this up to our membership team to see if they can provide a further explanation.
Hi @John_Vu ,
Thanks for reply. I re-checked and verified that there is only one workspace named Timely.
Please check the attached screenshot for reference:
