Skip to main content

Hello!


I am currently working on setting up Figma scim provisioning between our IDP and the Figma application. A couple questions.




  1. I cannot access previously created accounts that weren’t created through SCIM through the SCIM API. Why? SCIM is supposed to just be a compatibility API layer that goes on top of Identity backend data that makes it so that all applications have a common way to access this information.




  2. Because of previous step, I will have to go in and create a POST request via the .csv report I can download from Figma as an admin to actually create the account.




Does creating an Account with the same userName and externalId automatically link these accounts? How will i know these accounts are linked?




  1. Is there any risk that when I create these accounts via scim, it will overwrite projects and reset accounts?




  2. If I create an account, do I have to also transfer the seat configs via the scim api, or if I don’t, will seat status also be reset? (figmaPermission, devModePermission, figjamPermission)



Hey George, welcome to the community!

I see in our backend that our support team replied to your questions.

For visibility, here are the responses for the community who may also encounter this issue:


’ You can use SCIM to manage the permissions of the users as described in Manage seats via SCIM. The files aren’t affected by the factor weather or not if you manage your users via SCIM or not. The assets remain in your org.


Currently, there’s no attribute in SCIM to provision a user with admin privileges thus the outcome of the test is expected that you lose your admin rights. In this case, Support can help you grant admin permission in the backend so you can become admin again.


Also, just to add extra context, Manage seats via SCIM is available for Enterprise plan only. If you need to utilize this feature, I’d recommend to consider upgrading to Enterprise plan. ’

Reply


Terms & ConditionsCookie settings