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.
To create an organization within Prismatic, first sign up.
For large organizations with multiple distinct divisions, consider creating an organization per division.
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.
After creating your organization, you will see a sample integration aptly named "Sample Integration" to help you get started with Prismatic. Feel free to delete the sample integration and create your own if you prefer.
- Web App
To edit any settings of your organization, click the Settings link on the left-hand sidebar. From this screen you can manage team members, credentials, alerting, and your subscription settings. You can also view your organization's utilization of Prismatic resources.
Your organization's name can be changed by clicking theon the top of the page. Your avatar icon can be changed by clicking the icon to the left of the search bar on the top of the page. Your avatar icon will likely be your company's logo. Avatars are cropped and resized to 512 x 512 pixels, and must be an image. Transparent square PNG images tend to look the best.
To rename your organization, use the
prism organization:update subcommand:
To update your organization's name programmatically, use the updateOrganization mutation:
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 + 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.
For More Information: Users
Credentials save login information (API keys, OAuth credentials, etc.) for integrations. Credentials are used by instances of integrations to interact with login-protected resources (Dropbox, AWS, SFTP servers, etc.).
Credentials saved at the organization level should be generic to all customers (for example, all of your customers might share an API key for some third-party service). If you need to create a set of credentials that pertain to a particular customer, create them from the customer page instead.
To add or edit credentials at the organization level, click the Settings link on the left-hand sidebar, and then select the Credentials tab. Be sure to click Save on the top right to save your changes.
For information on the types of credentials you can create, see authorization methods. To walk through a sample integration that uses configuration variables and credentials see this quickstart guide.
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 of an integration 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 alert group, click the Settings link on the left-hand sidebar, and then select the Alert Groups tab. Click the +Alert Group button to create a new alert group, and enter users to notify and webhooks to invoke in the even of an alert trigger.
For More Information: Monitoring and Alerting
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.
For More Information: Monitoring and Alerting
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
- Blog 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.
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.
Please reach out with any questions about billing.
You can delete your organization from the Subscription tab shown above. Note that deleting your organization is permanent.
Organizations with an Enterprise plan and their customers can opt to interact with the Prismatic platform through a custom domain.
For example, you might want your team members and customer users to access https