Skip to content

IAM - Render - update fields to match connector#379

Merged
jerann merged 1 commit intomainfrom
iam-render-updates
Mar 27, 2026
Merged

IAM - Render - update fields to match connector#379
jerann merged 1 commit intomainfrom
iam-render-updates

Conversation

@jerann
Copy link
Copy Markdown
Contributor

@jerann jerann commented Mar 27, 2026

image

Summary by cubic

Updated the Render IAM connection guide to match the connector fields. Replaced the API key steps with Team ID (from the Team Settings URL) and admin email/password, and added a screenshot of the credentials form to avoid setup confusion.

Written for commit b474f18. Summary will update on new commits.

Replace incorrect API Key guide with the actual required fields:
Team ID (from Team Settings URL), admin email, and admin password.
Copilot AI review requested due to automatic review settings March 27, 2026 11:18
@mintlify
Copy link
Copy Markdown
Contributor

mintlify bot commented Mar 27, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
stackone-hub 🟢 Ready View Preview Mar 27, 2026, 11:20 AM

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Render IAM connection guide to match the connector’s current authentication/field requirements, replacing the prior API-key-based instructions with Team ID + admin-credential guidance and an updated UI screenshot.

Changes:

  • Reworked render.mdx steps to focus on locating the Render Team ID and providing admin credentials.
  • Removed prior API key creation/copy instructions and related screenshots.
  • Added a new screenshot (image4.png) referenced by the updated guide.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File Description
images/render/image4.png Adds a new screenshot used by the updated Render IAM connection guide.
connection-guides/iam/render.mdx Updates the guide to instruct users to find the Team ID and use admin credentials, and references the new screenshot.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Upon reaching the Link Account page, enter the API Key from the previous step.
</Step>
Use the email address and password of the team admin account when connecting to StackOne.

Copy link

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The guide explains how to find the Team ID and then mentions using the admin email/password, but it never explicitly tells the user to enter the Team ID + admin credentials on the StackOne “Link Account” page and click Connect (this is called out in almost all other IAM connection guides). Consider adding a short block here that instructs entering the Team ID, admin email, and admin password on the Link Account page and proceeding with Connect (the screenshot can remain as supporting context).

Suggested change
<Steps>
<Step title="Open the StackOne Link Account page">
In the StackOne Hub, open the **Link Account** page for the Render connection.
</Step>
<Step title="Enter your Render details">
Paste the **Team ID** you copied earlier into the Team ID field, then enter the **admin email** and **admin password** for your Render team.
</Step>
<Step title="Connect the account">
Review the details and click **Connect** to link your Render account to StackOne.
</Step>
</Steps>

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Contributor

@mstrivens mstrivens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jerann jerann merged commit 6083233 into main Mar 27, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants