Create a Template
Creating a template is the first step toward building a reusable, versioned procedure in RAMP. A template serves as a container for one or more versions, each of which defines the actual steps, variables, and execution rules.
Prerequisites
Section titled “Prerequisites”- You must have the Create Template permission in your current tenant.
- At least one category must exist (configured by administrators).
Creating a new template
Section titled “Creating a new template”- Navigate to the Templates page from the main sidebar.
- Click the New Template button in the top-right corner.
- Fill in the required fields in the creation dialog.
- Click Create to save the template.
You will be redirected to the template detail page where you can begin adding versions and steps.
Template fields
Section titled “Template fields”Title (required)
Section titled “Title (required)”The template title is a human-readable name that identifies the procedure. Choose a descriptive title that clearly communicates the purpose of the runbook.
Examples of good template titles:
- “Database Backup Procedure — Production”
- “Application Deployment Checklist v2”
- “Incident Response — Network Outage”
Category (required)
Section titled “Category (required)”Select a category to organize the template within your library. Categories help users filter and find templates quickly.
Tags (optional)
Section titled “Tags (optional)”Tags provide flexible, free-form categorization beyond the single category assignment. You can add multiple tags to a template.
To add a tag:
- Type the tag name in the tags input field.
- Press Enter or click Add Tag to add it.
- Tags appear as chips below the input. Click the delete icon on any chip to remove it.
Tags are useful for cross-cutting concerns like:
- Environment labels:
production,staging,development - Team labels:
infrastructure,database,security - Priority labels:
critical,routine,emergency
What happens after creation
Section titled “What happens after creation”When you create a template, RAMP automatically:
- Creates the template record with your selected title, category, and tags.
- Creates an initial Draft version (the first version of your template).
- Redirects you to the template detail page.
From there, you can:
- Open the draft version in the version editor to add steps and variables.
- Assign team members to the template.
- Configure system restrictions.
System association
Section titled “System association”Templates can optionally be associated with a system (managed system). This association is not set during creation but can be configured on the template detail page. When a system is assigned:
- The template appears when filtering by that system.
- Instances created from this template inherit the system context.
- System restrictions can control which stages the template may be used for.
Template lifecycle overview
Section titled “Template lifecycle overview”After creation, a template follows this lifecycle:
- Create — Template is created with an initial draft version.
- Edit — Add steps, variables, and configure the draft version in the version editor.
- Publish — Publish the draft to create an immutable versioned snapshot.
- Approve — Optionally route the published version through an approval workflow.
- Use — Create instances from approved versions.
- Iterate — Create new draft versions based on previous ones, repeating the cycle.