Understanding the Permit Type Builder

The Permit Type Builder allows you to create and configure permit types that define how parkers can access parking within your system.

Permit types replace traditional registration settings with a more flexible, scalable way to manage parking. They allow you to control who can park, when they can park, how long they can stay, and how much they pay—all in one place.

This article walks through the full workflow of creating a permit type at a high level, so you understand the key components and how they fit together.

Details

Permit Type Name

The Permit Type Name is the label that parkers will see when selecting a parking option.

• This should be clear and descriptive
• Use naming that reflects the use case (e.g., Monthly Parking, Visitor Parking, Evening Permit)
• Avoid internal terminology that may confuse end users

This is one of the most important fields for user experience.

Description

The Description provides additional context about the permit type.

• Explain who the permit is for
• Keep it short and easy to scan

Example: Valid for visitor parking. Maximum stay of 2 hours. No overnight parking permitted.

Enabled in Portal

This setting controls whether the permit type is available in the portal.

• Enabled → the permit type can be accessed by parkers
• Disabled → the permit type is not visible in any user-facing portal flows

When enabled, the permit type can be accessed:

• Via its global link (generated on the permit type)
• Through tenant or location lookup links where the permit type is assigned

Use this to control when a permit type is live without removing or reconfiguring it.

Enabled in Dashboard

This setting controls whether the permit type is active and available.

• Enabled → can be used to create permits in the dashboard
• Disabled → create flow is hidden from all user account-facing flows

You can use this to:

• Prepare permit types in advance through the dashboard
• Temporarily disable access without deleting configuration

Sort Priority

The Sort Priority determines the order in which permit types appear to parkers.

• Lower numbers = higher priority (shown first)
• Helps guide users toward the most relevant options

Recommended:

• Prioritize most common or preferred options at the top
• Use consistent spacing (e.g., 1, 10, 20) for flexibility later

Parking

The Parking section defines how the permit behaves in practice. This is where you configure when, where, and how a permit can be used.

It is made up of two parts:

• Parking Settings (per option)
• Global Rules (apply to the entire permit type)

Parking Settings

Parking settings are configured through Parking Options. Each option represents a specific parking configuration (e.g., different durations, times, or prices).

You can create one or multiple parking options depending on your use case.

Each parking option includes:

Dates and Times

Defines when the permit is valid.

You can choose from different scheduling types:

• Specific Date(s)
  Set exact dates and times for parking
• Date Range(s)
  Define a start and end date
• Flexible Time
  Allow users to choose start and/or end times based on rules

Flexible time options allow you to control:

• When a permit can start (e.g., user-selected, specific days)
• When it expires (e.g., after duration, same day, specific time)

You can also add additional restrictions, such as:

• Minimum or maximum duration
• Time increments
• Daily time windows
• Availability windows (when registration is allowed)

Use flexible time when you want to give parkers control, and fixed dates when the schedule is predefined.

Locations

Where the permit is valid

• Select one or more locations
• Optionally require users to choose a location during registration
• Supports location-based capacity (if enabled)

This allows a single permit type to work across multiple parking areas.

Pricing

Defines how much the permit costs.

• Choose a pricing type (e.g., flat rate)
• Set the total price for the parking option
• Option to charge or offer free parking

Pricing applies to the entire parking option, not per day.

Example: A $10 flat rate for a 3-day option = $10 total, not $10/day

Global Rules

Global rules apply to the entire permit type, across all parking options.

Permit Limit

Limits the total number of permits that can be issued.

• Helps manage capacity across all users
• Prevents over-allocation

Max Plates per Permit

How many license plates can be associated with a single permit.

• Example:
  • 1 plate → one vehicle per permit
  • Multiple plates → shared or multi-vehicle permits

All plates on a permit are considered active for enforcement.

Hide Future Parking Options

Controls how future availability is displayed.

• Enabled → only currently active parking options are shown
• Disabled → future options are visible in advance

Useful for simplifying the experience when future options shouldn’t be selectable yet.

Summary

The Parking section allows you to:

• Define when permits are valid
• Control where they can be used
• Set pricing and duration
• Apply global constraints across all options

By combining parking options with global rules, you can support both simple and complex parking configurations within a single permit type.

Directions

The Directions section allows you to provide parkers with clear guidance on where to park.

This helps ensure users arrive at the correct location, especially when a permit type is valid across multiple areas.

Parking Location

Used to guide parkers to the correct parking destination.

• Displays the address and link to map of the parking location
• Can be edited to update location details or adjust mapping

These directions are shown to parkers in the portal after selecting or purchasing a permit.

When to use Directions

Use this section when:

• Parking locations may be difficult to find
• You want to provide additional clarity or confirmation
• A permit type applies to specific or multiple locations

Tenants

The Tenants step allows you to control who can access a permit type, apply optional limits, and manage tenant-specific portal links.

This step is optional but recommended when you want to restrict access or track permits by tenant.

What this step does

Using tenants, you can:

• Define eligibility
  Control which tenants can create permits using this permit type
• Tag permits with tenant context
  Helps with reporting, enforcement, and integrations
• Apply tenant-level limits
  Set additional caps per tenant (optional)
• Generate tenant-specific portal links
  Provide direct access links for specific tenant groups

Adding Tenants

Use the tenant picker to search and select tenants.

Supported tenants include:

• Tenants connected to the selected location(s)
• Global tenants (not tied to a location)

Each selected tenant will appear as a row in the list.

Tenant Row Configuration

Each tenant includes the following controls:

Portal Link

Each tenant can have its own portal link.

• Enable → generates a unique link for that tenant
• Copy → copies the link to your clipboard
• Download QR → downloads a QR code for sharing
• Regenerate → creates a new link (confirmation required)

Regenerating a link will invalidate the previous link.

Use tenant links when you want to:

• Share access with a specific group
• Track usage by tenant

Permit Limit

Set a maximum number of permits that can be issued for this tenant.

• Toggle ON → enter a numeric limit
• Toggle OFF → treated as Unlimited

Plate Limit

Set a maximum number of plates per permit for this tenant.

• Toggle ON → enter a numeric limit
• Toggle OFF → treated as Unlimited

How Limits Work

Tenant limits are optional additional caps.

They work alongside other limits in the system:

• Permit Type limits
• Parking option / location limits
• Tenant limits

Rule:

The most restrictive limit always applies

Example:

• Permit Type limit = 100
• Tenant limit = 50
  → Effective limit = 50

Behaviour & Interactions

• Adding a tenant → appears immediately in the list
• Removing a tenant → removes instantly (no confirmation)
• Limits are optional and do not require input
• Portal links are created and managed per tenant

Summary

The Tenants step allows you to:

• Control who can access a permit type
• Apply optional per-tenant limits
• Generate tenant-specific access links
• Add context and structure to permits

If no tenants are added, the permit type is available to all users based on other configuration.

Codes

The Codes step allows you to restrict access to a permit type using access codes.

This is useful when you want to limit registration to a specific group of users, such as employees, residents, or event attendees.

Require Codes to Register

Enable this setting to require users to enter a valid code before they can register for a permit.

• Enabled → only users with a valid code can access the permit
• Disabled → permit is available without a code

Use this when access should be restricted or controlled.

Code Management Modes

There are two ways to manage codes:

1) Basic Mode

Use a single shared code for all users.

• Simple to set up
• Best for small groups or low-control scenarios

2) Advanced Mode

Enable Advanced to manage multiple codes with additional controls.

This unlocks:

• A dedicated Codes table
• Per-code limits and configuration
• Additional metadata per code

Recommended for larger groups or when tracking usage is important.

Managing Codes

In Advanced mode, you can create and manage multiple codes.

Each code includes:

1) Code

The value users must enter to gain access.

• Must be unique
• Can be shared or distributed as needed

2) Override Use Limit (Optional)

Override the default usage limit for this specific code.

• If enabled, the code will use its own limit
• If reset, it will return to the override value

3) Advanced Code Settings

When Advanced mode is enabled, additional configuration becomes available:

Title

Controls the label shown to users in the portal.

Example: “Access Code” or “Employee Code”

Description

Provides instructions or context for users.

Example: "Enter the code provided by your employer"

Limit Code Usage

Restrict the total number of times a code can be used.

• Applies across all users
• Helps control distribution and reuse

Limit Permits per Code

Restrict how many permits can be created using a single code at one time.

• Useful for group-based allocations

Additional Information (Optional)

Store extra data on codes.

Examples:

• Name
• Employee ID
• Internal reference

This can be used for tracking purposes.

Behaviour & Interactions

• Codes are managed in a searchable table
• New codes can be added individually
• No codes → no access (if “Require codes” is enabled)
• Advanced mode enables full code lifecycle management

Summary

The Codes step allows you to:

• Restrict access to specific users
• Control how permits are distributed
• Track and manage usage through individual codes

You can use simple shared codes or advanced configurations depending on your needs.

Settings

The Settings step allows you to customize the registration experience, collect additional information, and control how parkers interact with their permits.

This step is optional and is typically used to tailor the experience to your specific operational needs.

Additional Information

Enable this setting to collect extra information from parkers during registration.

• Add custom fields such as:
  • Name
  • Employee ID
  • Unit number
  • Any other identifiers

Field Configuration

Each field includes:

• Label
  The name of the field shown to parkers
• Input Type
  • Text input
  • Dropdown (with predefined options)
• Required
  Mark whether the field must be completed
• Description (optional)
  Provide context or instructions
• Tenant Assignment (optional)
  Restrict the field to specific tenants

Branding

Upload a logo to customize the permit type experience. 

• Displayed in the portal during registration
• Helps align the experience with your organization or client

Instructions

Add custom instructions that are shown to parkers at different stages of the experience.

If left blank, default location-level instructions will be used.

Pre-registration Instructions

Displayed before the user begins registration.

Registration Confirmation Instructions

Shown after a permit is successfully created.

Expiring Soon Instructions

Used in reminder emails and SMS messages before a permit expires.

Notifications & Files

SMS Expiry Notifications

Enable to send reminder messages to users before their permit expires.

• Uses the Expiring Soon Instructions content
• Sent to users who have opted in

Add Files

Upload files to share with parkers.

• Up to 3 files supported
• Included in:
  • Portal experience
  • Email communications

Examples:

• Parking maps
• Instruction guides
• Policy documents

Parker Controls

Parker Controls give you the option to add self-service flexibility for parkers.

When enabled, parkers can make updates like editing their plate or canceling their permit directly from their confirmation email, without needing to contact your team for help.

Parker Email is Required

Require parkers to enter an email address.

Used for receipts and notifications

Allow Parkers to Edit

Allow users to update their own permit details after registration.

This is commonly used for things like correcting or updating a license plate.

Allow Parkers to Delete

Allow users to cancel or delete their permit.

Ready to get started?