Credential requests

the credential requests feature is available to official make partners and enterprise customers only users with the required permissions and with this feature enabled can create credential requests see below docid\ oktctqxdzqevdudaz3ifh docid\ oktctqxdzqevdudaz3ifh credential requests are a secure, scalable, and user friendly way to collect connection credentials from third parties when building automations in make (e g , for teammates, other teams, clients, or external partners), builders (requesters) can specify which connections and credentials are required for a scenario and generate a secure request link recipients can use this link to provide the requested connection credentials if they are not part of the requester's make organization or team, they are invited to join it with a guest r ole before they provide the credentials if they are already part of the requester's make organization, they can provide the credentials directly in both cases, recipients can see who requested their credentials and how they will be used re tain the ongoing control to revoke, reauthorize, or edit credentials at any time login credentials and other authentication data are never exposed through credential requests the person authorizing the request enters credentials directly in make to create the connection this connection can be used to build scenarios, but no one on the requester's side can view, access or retrieve the user's authentication details (e g , passwords, api keys, oauth credentials) how to enable credentials requests feature to enable the feature, each user must submit this https //f make com/r/credential requests the customer care team then verifies the eligibility (partner or enterprise account user with a corporate email) and grant acceess to the feature upon approval the feature is enabled for a user, not the organization once a user has access to the credentials request feature, they can use it in every make organization they are part of all owners of these organizations will receive an email notification that this member has been granted permission to use the feature in their organization the same applies to any new organizations the user joins in the future all team members can check which users have the feature enabled by navigating to team > team members tab in the left sidebar who can request credentials credential r equests are created and sent from the team you're currently working in within your make organization who you can send a request to depends on your team and organization role team members can request credentials from any user within their team team admins can request credentials from any user within their organization organization admins and owners can request credentials from any user within their organization and from external people once the recipient authorizes a request, everyone in the team can use the shared credentials to create connections in the scenarios https //help make com/audit logs show when and b y whom a credential request was created, deleted, or authorized organization admins can see this information for the entire organization team admins can see this information for their teams create credential request to create and send credential requests, you must have this feature enabled to create a credential request in the left sidebar, click credentials and switch to the credential requests tab click the +create request button in the request name field, enter a descriptive name that will help identify the request (e g , the project or automation name) in the recipient section , select recipient is part of \[name of your organization] organization , if you want to request credentials from someone within your make organization example you are building an internal weekly newsletter for all company employees you want to automate email delivery and create newsletters tailored to each employee's role, location, or group or team they belong to, to provide the most accurate and targeted information to do that, you need access to employee data stored in the company's identity provider (microsoft entra id) if you don't have access to it, you can send a credential request to get access to the following modules microsoft entra id > search users, get a user, get a user's memberships, search groups, get a group a colleague with access to these credentials can review your request, verify that it only includes read access, and create a connection for you you then query entra id to retrieve email addresses and related information in this case, you will select a user from the drop down list if you want to request credentials from someone who is not part of your make organization, select recipient is not part of \[name of your organization] organization example you are an external contractor hired to help the marketing department automate lead generation you need to create a scenario in make that retrieves emails from the marketing team's email account and stores or updates contacts in their hubspot crm you can request the m arketing manager to create the connection to the following a pps and modules email > get emails hubspot > search for contacts, get a contact, create or update a contact once you get all the credentials, you can build a scenario for the entire marketing team or for a specific marketing manager this option is only available to those with permission to https //help make com/organizations#1ikqb you need to have either an admin or an owner https //help make com/organizations#em3xi in this case enter the recipient's name and email address optionally, add a description (max 256 characters) to explain the purpose of the request once finished, click next in the app field, select the app for which you want to request credentials if the app has multiple versions, select the required one in the version field in the module field, select the modules for which you want to request credentials to include all the modules, click select all optionally, add a note (max 256 characters) explaining why you need the credentials and how you'll use them, or specify other details configure a name to distinguish these credentials afterward in the list of available connections for the app, or leave the default to add more apps to the request, click the +add app button and repeat the steps explained above review the terms and conditions, then check the box to confirm your agreement click submit you'll see a confirmation that the request has been successfully sent a recipient who is not a part of your make organization will be invited to join your organization and team with a guest role a recipient who is a part of your make organization will receive a link to review the request authorize or decline a credential request as a recipient once a requester submits a request, the recipient gets an email notification to authorize the credential request as a recipient open the email notification if you're a part of the requester's make organization, click the review request button if you're not a part of the requester's make organization, you'll get an invitation to join it click the accept invitation button follow the prompts to log in to make or sign up if you don't have an account once you log in to make , you will be redirected to the request details page in the requester's organization there, you can see request name requester's name request date request description (if provided by the requester) in the requested credentials section, you can see the apps for which credentials are requested hover over the modules and permissions under each app to see which ones are included in the request click authorize to proceed a window prompting you to create a connection will appear follow the prompts to grant make access depending on the connection, you may need to select the connection type, enter an api key, oauth credentials, or other authentication details once finished, a green authorized label should appear next to the app's name to decline the credential request, as a recipient log in to make switch to the requester's organization, if you have several in the left sidebar, click credentials click details next to the relevant request click decline next to the app you don't want to provide credentials for add the reason for declining the request click decline the requester will see the red declined label in the request and the reason for that view credentials requests to see all the sent and received credential requests, click credentials on the left sidebar in the credential requests tab, you can switch between sent and received requests depending on whether you are a requester, a recipient, or both sent requests in the sent tab, you can view all the requests sent by you and your team members, including request name which apps are included in the request who requested the credentials who the recipient is when the request was sent request status requests can have the following statuses authorized all apps in the request have been authorized partially authorized some apps have been authorized, and others declined incomplete the authorization process hasn't been completed invalid the authorization process has failed declined the request has been declined view request details as a requester to see all available information for the request, click details next to the credential request for sent requests, the details include the recipient's name and email address the request submission date the request description (if provided by the requester) in the requested credentials section, you can also see all the apps included in the request hover over modules and permissions to see what access is authorized see whether the request for a particular app is still pending , has been authorized, or declined (with the reason added by the recipient) received requests in the received tab, you can view all the requests you've received, including request name which apps are included in the request who requested the credentials when the request was sent request status view request details as a recipient to see all available information for the request, click details next to the credential request for received requests, the details include the requester's name and email address the request submission date the request description (if provided by the requester) in the requested credentials section, you can also see all the apps included in the request hover over modules and permissions to see what exactly is authorized see whether the request has been authorized or declined (with the reason you added) revoke, authorize , or decline access to the credentials revoke access to credentials a recipient can revoke access to the provided credentials at any time to do that in the left sidebar, click credentials switch to sent in the credential requests tab, and click details next to the relevant request in the requested credentials section, click revoke for the app you want to remove the access from the requester will no longer be able to use your credentials for that app to restore access, click authorize and follow the prompts to establish the connection again (e g , grant access, enter api key) to permanently remove access , click decline or delete the request (see below) the requester will no longer be able to use the credentials provided by the recipient for a particular app in the request however, if there are multiple apps in the request, all the other authorized credentials will still be available delete credential request both a recipient and a requester can delete the entire credential request to do that in the left sidebar, click credentials if you're a requester switch to sent in the credential requests tab click the three dots > delete next to the request review the list of connections where the credentials are used and click delete to confirm if you're a recipient switch to received in the credential requests tab click the three dots > delete next to the request review the list of connections where the credentials are used and click delete to confirm in both cases, the request will be deleted the requester will no longer be able to use the credentials provided by the recipient for all the apps included in that request faqs how long is a credential request link valid? links don't expire, but recipients should act within a reasonable timeframe if they don't respond, you can follow up or send a new request can i cancel a request in progress? yes, delete the request, and the recipient loses access to all apps in it what if the recipient's email address changes? if an external recipient can't access their email, send a new request with their updated email address you can delete the old request can i request credentials from multiple people at once? you need to send separate requests to each person you can't bundle multiple recipients in one request can the recipient see what i do with their credentials? recipients can see which modules are included in the request and can revoke access anytime they can't see the specific data you access with those credentials what if the recipient's credentials expire? connections may stop working if authentication expires (e g , token refresh fails) the requester will see an error and should contact the recipient to re authorize can i change my mind and stop sharing credentials? yes, revoke access anytime the requester loses immediate access, but the request stays open if you want to permanently cut off access, delete the request is it safe to share credentials ? yes, your login and other authentication data are never exposed through credential requests when authorizing a request, you enter your credentials directly in make to create the connection this connection can be used to build scenarios, but no one on the requester's side can view, access or retrieve your authentication details (e g , passwords, api keys, oauth credentials)