Can a Super Admin user check what users exists and...
# support
a
I'm trying to transfer property of one project from user A to userB. But, when user B tries to login it just return a HTTP 410 Gone status.
r
@alexisrodgtz do you mind sharing how you are trying to transfer ownership, and what you're trying to accomplish at a high level?
a
I created several projects. I cannot create Client's credential for each Project from the Super Admin view. So, I'm trying to move an User to each project, for creating a Client and extract
client_id
and
client_secret
. I want to keep the scope of the patients I'm working on inside a Project resource.
There is a way to get those Client Id and Secret using admin cli? https://www.medplum.com/docs/self-hosting/super-admin-cli
r
We have an admin endpoint to create clientApplications here: https://www.medplum.com/docs/api/project-admin/client
a
Thank you! I didn't see that before 😅
r
🙂
It's ok, that doc is fairly new
If you have any advice on how we can make it easier to find, we'd love the feedback. Would love to know what terms you searched, etc.
a
I try serching
Client
,
Create Client
,
client id
,
client secret
WOW, works great at the firts try!!! This will save a lot of time. Thank you again!!
r
Great!
If you don't mind sharing, I'd love to learn more about your use case, organization, and how you're thinking about projects.
This idea of programatically creating client ids is fairly new for us, so wanted to understand it better
a
Sure. We are managing patient for several clinics. I found We can keep Patients separated by Projects, allowing only the Super Admin to see all Patients in the platform when needed. Also, for patient deduplication we want to do it only in a Project Scope. Rn, I'm just testing how to programatically deal with Project, Clients, and Patient creation. Webapp is really helpful to validate I'm understanding how the FHIR api behaves.
I tried to keep them separate by Organizations, but seems that's not the use case that for that resource.
r
Thank you so much for sharing! That makes a lot of sense. We also support what is called the "cross organizational model" via access policies (see example 2c here: https://github.com/medplum/medplum/discussions/1453)
The main difference would be the role of providers, and whether or not they can be part of multiple orgnaizations
We have some docs on the way that will describe how to set this up via
AccessPolicy
resources, but if this is interesting to you, we can get those out sooner
a
Thanks! Will check and let you know if help me to implement a more clerar structure
172 Views