Typically, each of your customers would have their own Cyclr “Account” where you can keep their data, integrations and Connectors separate from your other customers’ data.
To create a new Account from the Console, go to Accounts > Account Management, and select the Add New Account button.
Adding or Updating an Account #
The following options are available when creating a new Account or editing an existing one:
| Property | Description |
|---|---|
| API ID | Enables you to provide a custom unique identifier for an Account. This will be used as the X-Cyclr-Account HTTP Header when making calls to Cyclr’s API to set the Account context being worked in.For convenience, you may choose to set it as the same unique identifier you have in your own application that identifies a customer. If left blank when creating an Account, Cyclr will copy its own unique internal “ID” value for this. |
| Name | A way to identify an Account through Cyclr’s interface and within reporting. |
| Description | Additional information about an Account |
| Timezones | The timezone to use when displaying date/time values within the Account. |
| Next Billing Date | |
| Account Audit Info | Allows you to enter additional information about an Account for your own reference. |
| Task Audit Info | Allows you to enter additional information about an Account for your own reference. |
| Concurrent Transaction Limit | Sets the maximum number of Transactions Cyclr will process within the Account at a time across all of its Cycles. Can be used to reduce the speed at which Cyclr processes the Transactions within an Account. Different Accounts can have different Concurrent Transaction Limits set, allowing one Account to process more Transactions at a time than another, enabling you to balance your Accounts’ processing speeds. This is particularly useful on a Private Cyclr Instance to avoid making too high a demand on your Instance’s resources. |
| Successful Transaction Data Retention | Overrides the Console-level setting. Allows you to specify how long successful transactions are kept. |
| Errored Transaction Data Retention | Overrides the Console-level setting. Allows you to specify how long failed transactions are kept. |
| Transaction Error Webhook | Overrides the Console-level setting. Makes an HTTP call when an error occurs in a transaction. Read more on handling errors. |
We have a full tutorial course on Account and User Management available for registered Community Site users.