
Emma Brennan asked a question.
If I do give them an API key, then they will have access to every folder in the ShareFile system, right? Not just theirs?
Thanks!

Emma Brennan asked a question.
If I do give them an API key, then they will have access to every folder in the ShareFile system, right? Not just theirs?
Thanks!
Hi Emma,
An API key in ShareFile only provides access to our public APIs. It does not, by itself, grant access to any data or folders.
A user's access is still determined by the ShareFile account they authenticate with when obtaining an access token. As a result, the API can only perform actions and access content that the authenticated user already has permission to access within ShareFile.
If the user is a client user, they would generally be limited to the folders and data that have been shared with them. They would not automatically gain access to every folder in the ShareFile account simply because they are using an API key.
Regarding API key creation, client users cannot create their own API keys. An employee user with the Manage Account-Wide Policies permission would need to create the API key on their behalf, or the client user would need to be upgraded to an employee user with the appropriate administrative permissions to create and manage their own API keys.

Okay! That makes sense. From what I'm understanding, as long as they have the client secret, URI redirect, and client ID and use their own login, they will be able to just do what they need to do with their own folder? So I will be able to give them the API key I generated, but it limits them to just the folder they have shared with them (if they are a client user).
Thank you for your reply! :)
Correct, they should get a 403 response code if they try to traverse a folder where they do not have any access to.
Hi Emma,
An API key in ShareFile only provides access to our public APIs. It does not, by itself, grant access to any data or folders.
A user's access is still determined by the ShareFile account they authenticate with when obtaining an access token. As a result, the API can only perform actions and access content that the authenticated user already has permission to access within ShareFile.
If the user is a client user, they would generally be limited to the folders and data that have been shared with them. They would not automatically gain access to every folder in the ShareFile account simply because they are using an API key.
Regarding API key creation, client users cannot create their own API keys. An employee user with the Manage Account-Wide Policies permission would need to create the API key on their behalf, or the client user would need to be upgraded to an employee user with the appropriate administrative permissions to create and manage their own API keys.