Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/connector.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,12 @@ sidebarTitle: "Coupa"
| Groups | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | <Icon icon="square-check" iconType="solid" color="#c937ae"/> |
| Roles | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | <Icon icon="square-check" iconType="solid" color="#c937ae"/> |
| Licenses | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | <Icon icon="square-check" iconType="solid" color="#c937ae"/> |
| Billing Accounts ² | <Icon icon="square-check" iconType="solid" color="#c937ae"/> | <Icon icon="square-check" iconType="solid" color="#c937ae"/> |

¹ Account Groups sync is opt-in. To enable it, select **Account Groups** in the resource types to sync when configuring the connector in C1, and ensure the `core.accounting.read` OAuth scope is added to your Coupa OAuth client.

² Billing Accounts sync requires the `core.accounting.read` OAuth scope. Provisioning (grant/revoke) additionally requires the `core.accounting.write` OAuth scope.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The Account Groups footnote (¹) mentions that sync is opt-in and tells users to select the resource type in C1. Is Billing Accounts also opt-in? If so, it would be helpful to add similar guidance here (e.g., "To enable it, select Billing Accounts in the resource types to sync…"). If it syncs by default (whenever the scope is present), then the current wording is fine — but it might be worth stating that explicitly to distinguish it from Account Groups.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The Account Groups footnote (¹) tells users that sync is opt-in and how to enable it. The Billing Accounts footnote (²) only mentions the OAuth scope requirement but is silent on whether it's opt-in or automatic.

If Billing Accounts is also opt-in, consider adding similar guidance:

Suggested change
² Billing Accounts sync requires the `core.accounting.read` OAuth scope. Provisioning (grant/revoke) additionally requires the `core.accounting.write` OAuth scope.
² Billing Accounts sync is opt-in. To enable it, select **Billing Accounts** in the resource types to sync when configuring the connector in C1, and ensure the `core.accounting.read` OAuth scope is added to your Coupa OAuth client. Provisioning (grant/revoke) additionally requires the `core.accounting.write` OAuth scope.

If it syncs automatically whenever the scope is present, the current wording works — but stating that explicitly would help distinguish it from Account Groups.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The Account Groups footnote (¹) explains that sync is opt-in and tells users how to enable it. This footnote only mentions scope requirements but doesn't clarify whether Billing Accounts sync is opt-in or automatic.

If opt-in, consider adding similar guidance:

Suggested change
² Billing Accounts sync requires the `core.accounting.read` OAuth scope. Provisioning (grant/revoke) additionally requires the `core.accounting.write` OAuth scope.
² Billing Accounts sync is opt-in. To enable it, select **Billing Accounts** in the resource types to sync when configuring the connector in C1, and ensure the `core.accounting.read` OAuth scope is added to your Coupa OAuth client. Provisioning (grant/revoke) additionally requires the `core.accounting.write` OAuth scope.

If it syncs automatically whenever the scope is present, stating that explicitly would help distinguish it from Account Groups.


### Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step.
Expand Down Expand Up @@ -77,7 +80,7 @@ A user with **Admin** access in Coupa must perform this task.
- openid
- profile

**If you also want to sync Account Groups, add:**
**If you also want to sync Account Groups or Billing Accounts, add:**
- core.accounting.read

**You'll need these scopes to give C1 READ/WRITE access (syncing access data and provisioning access):**
Expand All @@ -94,8 +97,9 @@ A user with **Admin** access in Coupa must perform this task.
- openid
- profile

**If you also want to sync and provision Account Groups, add:**
**If you also want to sync and provision Account Groups or Billing Accounts, add:**
- core.accounting.read
- core.accounting.write (required for Billing Account provisioning)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nit: "Billing Account" (singular) here vs "Billing Accounts" (plural) used everywhere else in this PR. Consider making it consistent:

Suggested change
- core.accounting.write (required for Billing Account provisioning)
- core.accounting.write (required for Billing Accounts provisioning)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nit: "Billing Account" (singular) is inconsistent with "Billing Accounts" (plural) used everywhere else in this PR.

Suggested change
- core.accounting.write (required for Billing Account provisioning)
- core.accounting.write (required for Billing Accounts provisioning)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nit: "Billing Account" (singular) is inconsistent with "Billing Accounts" (plural) used everywhere else in this PR.

Suggested change
- core.accounting.write (required for Billing Account provisioning)
- core.accounting.write (required for Billing Accounts provisioning)

</Step>
<Step>
At the bottom of the page click **Save**.
Expand Down
Loading