Settings

Organization-wide configuration lives under Settings in the Suger Console. These pages cover the settings a team changes after setup: who receives which notification emails, where files and exports go, how CRM data fills a private offer, where buyers land after a marketplace purchase, how your own systems call Suger and receive its events, and the quotas on what you can provision. Users, roles, MFA, and single sign-on are covered in Account.

Find the setting you need

Open Settings from the console’s left navigation; each page below says where in Settings its options live.

Notify your team and keep records

Page	What you use it for
Email Notification	Route each notification event to the right recipients, customize the emails with templates, and test a template before it reaches anyone.
Files	Find, view, and download legal agreements, order forms, brand assets, and integration logs in one place.

Get data out

Page	What you use it for
Table Export	Export table data once or on a schedule — as a CSV, JSON, or Parquet download, or into Snowflake, Google BigQuery, Google Storage, or Databricks.

Page	What you use it for
Private Offer Field Mapping	Decide how Salesforce or HubSpot data populates the fields of a marketplace private offer, test the product-list filter, and tag products by product line.
Signup URL Redirect	Send a buyer from the marketplace to your own signup page after purchase, including the Azure specifics.

Build against the Suger API

Page	What you use it for
API Access	Call the Suger API with the OAuth 2.0 client-credentials flow, or the legacy API client.
Webhook	Subscribe your own backend to Suger events, verify each delivery’s signature, and handle retries.

Know your limits

Page	What you use it for
Service Quotas	See how many resources you can provision, where to view the limits, and how to request an increase.

Scope and limits

Spotted something wrong or out of date on this page? Tell us and we'll correct it.