Settings and administration

Configure Launchpad for your tenant - organization, categories, types, custom fields, lists, submission rules, access scopes, lifecycle, assessment, business case, users and the audit log.

Open Administration ▸ Settings. Inside settings the rail becomes the settings menu; select Back to Launchpad to return. Viewing settings needs launchpad_configuration view (for example Launchpad Program Manager); changing them needs edit (Launchpad Administrator). Users & roles needs users.view and Audit log needs audit.view. Group Pages Organization Organization, Categories, Access scopes Opportunities Opportunity types, Custom fields, Lists, Submission rules Governance Lifecycle, Assessment Business case Business case People & audit Users & roles, Audit log Organization and regions# Organization holds two trees: the organization (business units, with departments and teams beneath them) and Locations and regions. Opportunities and applications pick their business unit, department and country / region from them. Select Add to add a top-level entry, or + on a row to add one beneath it. Set its name, kind (Business unit, Department or Team), code and owner. Use the pencil to edit and the bin to delete. Categories is a tree of process categories (for example Finance & Accounting ▸ Procure-to-Pay), edited the same way, with an owner and description. Opportunity types# The types a submitter chooses from: RPA Automation, Agentic Automation, Document Automation, Test Automation, API / Integration Automation, Workflow / Business Process Automation, Existing Automation Improvement and Other. Select Add type to add one with a key, name, description and icon; edit a type to rename it or make it inactive. Custom fields# Add your own fields to opportunities or applications: Select Add field. Enter the Name and Key, choose whether it is for Opportunities or Applications, and pick the Type: text, multi-line text, number, date, date and time, yes/no, single or multiple choice (with Options), URL or user. Optionally set a Group, a Description, Only for these types and Only in this category (and beneath). Select Add field. Opportunity fields appear on the Expected benefits step of the submission and in Additional information on the opportunity. Archive hides a field from new entries without losing its values. Lists# Lists edits the values offered in Benefit types, Process frequencies, Document categories and Collaborator roles. Rename a value, tick Archived to stop offering it, or add a value and select Add; then select Save. For collaborator roles, Can edit decides whether people with that role can edit the opportunity. Submission rules# Under Mandatory fields, select the fields an opportunity must have before it can be submitted. By default these are Short description, Business problem and Opportunity types. Changes are saved at once. Under Duplicate detection, Also search by meaning finds similar opportunities that use different words. It is available when the tenant's AI features are on; otherwise duplicates match by wording only. Access scopes# To limit what a user or group sees to part of the organization: Under Who, choose User or Group and pick them. Under Scope, choose Organization unit or Category and pick the entry. Select Add scope. The person then sees only opportunities in that unit or category (and beneath), within their role. Removing their last scope gives them the whole tenant again. Lifecycle# Lifecycle shows the phases as a graph (bold amber arcs need an approval), the Phases table with each phase's stage and number of opportunities, and the Transitions table with each move's permission and requirements. Add phase: enter the Name, Key and Stage. A phase that holds opportunities can't be deleted. Add transition: choose From and To, the Permission the mover needs, the fields Required before the move, and whether it Needs an approval (by someone other than who asks) or Needs a linked automation. Export downloads the lifecycle and the newest assessment templates as a file; Import applies such a file (for example from another tenant); Reset restores the default lifecycle and assessment template. Assessment# Under Scoring, set the Hours of one FTE per year (1,800 by default) and the ease bands: High ease from (65) and Low ease below (35). Select Save. The templates table lists the assessment templates with their version, the types they apply to, the number of questions, the weight sum and how many assessments use them. Select a template to preview it, and New version of template to change its questions, weights and options (one per line as Label = score). Existing assessments keep the version they were made with; the opportunity shows A newer template exists. Business case# Set the money and forecast inputs: Rates: Currency (ISO 4217, for example USD), Hourly rate (values hours saved) and Robot-hour rate (values robot time). Without rates, benefits are shown in hours. Drift: Threshold (%), Minimum days and Minimum transactions before an opportunity can be marked drifting. Forecast and ranking: NPV discount rate (%), Horizon (years) and Vote weight (0–0.5) in the priority score. Cost catalogue: standard costs (name, One-time or Yearly, unit cost) that people add to business cases. Changing an item never rewrites an existing case; set Offered to Retired to stop offering it. Users & roles# Users & roles shows the tenant's Users, Groups and Roles inside Launchpad. It is the same screen as the Orchestrator's Manage access; see Manage access and Roles and access. Audit log# Audit log shows the tenant audit log narrowed to Launchpad: opportunities, applications, configuration and saved views. Search it, or select Show filters to filter it. See Audit and webhooks. Send notifications to webhooks or Teams# Every Launchpad notification is also published as the webhook event com.velophex.launchpad.notification, and only if the change was saved. Its data holds the event, the opportunity or application, a title, body and link, and in data.teams a ready Microsoft Teams message with an Open in Launchpad button. To post them to a Teams channel: In Teams, create a workflow that starts with When a Teams webhook request is received. Add a Post card in a chat or channel step and set its card to: TextCopytriggerBody()?['data']?['teams']?['attachments']?[0]?['content'] Subscribe the workflow's URL to com.velophex.launchpad.notification as a webhook. See Create a webhook. Next steps# Roles and access Launchpad overview

Organization and regions

Opportunity types

Custom fields

Lists

Submission rules

Access scopes

Lifecycle

Assessment

Business case

Users & roles

Audit log

Send notifications to webhooks or Teams

Next steps