Skip to main content

Organization Settings

In order to disambiguate who Prismatic's customers are, and who your customers are, we refer to Prismatic's customers as organizations and your customers as customers. For example, if you work for a company that develops project management software for rocket companies, your organization may be "Progix Software" with customers like "Rockets, Inc" and "Eastern Spaceflight".

Your organization can contain integrations for all of your products, and team members from multiple departments within your company can access the integrations you create. Your team members can be assigned roles, so your DevOps team members might have administrator access, while your support team might have permission to review integration logs.

Creating your organization​

To create an organization within Prismatic, first sign up.

For large organizations with multiple distinct divisions, consider creating an organization per division.

note

If your company has already created an organization, ask your organization's administrator to create a user account for you instead. Registering with Prismatic again will create a second organization.

Editing your organization​

To edit any settings of your organization, click the Settings link on the left-hand sidebar. From this screen you can manage team members, alerting, and your subscription settings. You can also view your organization's utilization of Prismatic resources.

Your organization's logo can be changed from the Theme tab. Logos are cropped and resized to 512 x 512 pixels, and must be an image. Transparent square PNG images tend to look the best.

Change logo for org in Prismatic app

Managing organization users​

After creating your organization, you can create accounts for your team members so that they can create and maintain integrations for your customers. Click the Settings link on the left-hand sidebar, and select the Team Members tab. Click the + Add team member button to create a new user. Select an appropriate role for your team member, and enter their name and email address. Once you create your team member's account, they will receive a confirmation email and registration link to set their password and personal information.

List of org users in Prismatic app

For More Information: Users

Organization single sign-On (SSO)​

As an organization with an Enterprise plan you can elect to authenticate your team members through your existing identity provider. If your team members sign in to other applications through Active Directory, Active Directory Federation Services (ADFS), or Lightweight Directory Access Protocol (LDAP), then we can configure your organization to sign in to Prismatic the same way.

If you use single sign-on (SSO), your team members will be redirected to your identity provider from the login screen if they enter an email address that matches your domain. Otherwise, they will be prompted for a password like usual.

Diagram showing paths and logic for SSO (single sign on)

If you are interested in using Single Sign-On for Prismatic, please reach out to our support team to get SSO configured and enabled for your organization.

Creating alert groups​

When instances of integrations behave unexpectedly, you likely want to be notified. For example, you may want your DevOps team to be alerted when an instance fails to run to completion. An alert group is a set of users to notify and webhooks to invoke when an alert trigger fires.

To create or modify an alert group, click the Settings link on the left-hand sidebar, and then select the Alert Groups tab. Click the + Add alert group button to create a new alert group, and enter users to notify and webhooks to invoke in the event of an alert trigger.

Create alert groups in Prismatic app

For More Information: Monitoring and Alerting

Using alert webhooks​

In addition to email and text alerts, you can configure alert monitors to invoke a webhook with a payload of your choice. To create or modify a webhook URL, click into the Settings page and select the Alert Webhooks tab. Click the +Alert Webhook button, enter an appropriate name for your alert webhook, and enter URL, header, and payload information for your webhook.

Alert webhooks can be used to invoke the PagerDuty API, your own DevOps alert endpoint, or any other alerting service with an HTTP-based API.

Add alert webhook in Prismatic app

For More Information: Monitoring and Alerting

Custom themes​

See the Embedding Marketplace article for information on custom theming.

Tracking service utilization​

You can track metrics about your organization's usage of Prismatic services from the Utilization tab of the Settings page. On this page, you can view details about:

  • Instance and integration counts
  • Blob storage usage
  • Instance execution count
  • Customer and user counts
  • Step Execution counts
  • Execution speed

Additionally, you can view metrics from this week and last week to help identify changes and anomalies.

Track organization usage of services in Prismatic app

Managing billing​

When you first sign up for Prismatic, you are entered into the "free plan" so you can try assembling and deploying a few integrations before paying for it. To view information on pricing, see our pricing page.

To manage billing within the web app, click Settings on the left-hand sidebar, and then open the Subscription tab. From there you can manage your subscription type, and update credit card and other billing information.

Manage organization billing in Prismatic app

Please reach out with any questions about billing.

Deleting your organization​

You can delete your organization from the Subscription tab shown above. Note that deleting your organization is permanent.

Custom domains​

As an organization with an Enterprise plan, you can choose to interact with the Prismatic platform through a custom domain that you control. For example, you might want to white-label Prismatic so your team members and customers access https://integrations.your-company.com instead of https://app.prismatic.io.

To configure a custom domain, please reach out to our support team, and let us know what subdomain (like https://integrations.your-company.com) you would like to use. We'll create an SOA record for that subdomain along with a few A and CNAME records for things like web app access, webhook invocation, and OAuth 2.0 callbacks:

  • https://integrations.your-company.com - web app and embedded URL
  • https://hooks.integrations.your-company.com - webhooks
  • https://**oauth2.integrations**.your-company.com - OAuth 2.0 callback

Once we have those records ready, you'll just need to create an NS record to point to a list of nameservers we'll provide you. Note: some DNS providers represent a list of NS servers as separate NS records (one server per record), and others have single NS records with a list of values.

Once your domain is white-labeled, your OAuth2 apps can use https://oauth2.integrations.your-company.com/callback as a callback URL.

Webhook and OAuth 2.0 URLs are derived from the URL you visit

Note that once a subdomain is configured, you can access your tenant through either the custom domain or the default Prismatic domain. Custom domains are not tenant-specific. If you have prod and dev tenants, both tenants can use the custom domain you establish.

  • If you access or embed Prismatic via https://app.prismatic.io, you will see webhook and OAuth URLs with the Prismatic domain.
  • If you access or embed Prismatic via your custom domain like https://integrations.your-company.com, you will see webhook and OAuth URLs with your custom domain.