Advanced Settings
Configure module naming, identifiers, and system settings
Advanced Settings
The Advanced tab contains system-level configuration for your module, including naming conventions, URL identifiers, and record behavior settings.
Accessing the Advanced Tab
- Go to Settings > Modules
- Select your module
- Click the Advanced tab
Module Naming
Control how your module is displayed throughout Coherence.
Display Name
The primary name shown in navigation, headers, and UI elements.
Example: "Contacts", "Support Tickets", "Project Tasks"
Singular Name
Used when referring to a single record.
Example: "Contact", "Ticket", "Task"
Appears in contexts like:
- "Create a new Contact"
- "View Task details"
- "Edit this Ticket"
Plural Name
Used when referring to multiple records.
Example: "Contacts", "Tickets", "Tasks"
Appears in contexts like:
- "View all Contacts"
- "3 Tickets selected"
- "Import Tasks"
Editing Module Names
- Click Edit Names in the Module Naming section
- Update the Display Name, Singular Name, and/or Plural Name
- Click Save Changes
Keep naming consistent. If your display name is "Support Tickets", use "Support Ticket" for singular and "Support Tickets" for plural.
Module Identifier (Slug)
The slug is the URL-safe identifier used in:
- Browser URLs (
/records/contacts/...) - API endpoints (
/api/modules/contacts/...) - Internal references and integrations
Viewing the Slug
The current slug is displayed in the Module Identifier section.
Changing the Slug
Changing a module slug will break existing bookmarks and external links to records in this module. Only change slugs when necessary.
- Click Change Slug
- Enter the new slug
- Review the warning about breaking existing links
- Click Change Slug to confirm
Slug Requirements
- Must start with a letter
- Can only contain lowercase letters, numbers, and hyphens
- Cannot contain spaces or special characters
- Must be unique across all modules
Valid examples: contacts, support-tickets, project-tasks-v2
Invalid examples: Contacts, support tickets, 123-tasks, tasks@work
Record Settings
Configure behavior for records in this module.
Allow Private Records
Default: Disabled
When enabled, users can create records visible only to themselves.
How it works:
- Create form shows a visibility selector
- Users can choose "Private" visibility
- Private records are only visible to their creator
Use cases:
- Personal notes or drafts
- Sensitive individual data
- Work-in-progress before sharing
When to disable:
- Collaborative modules where all data should be shared
- Compliance requirements for data visibility
- Team-based workflows
Toggling Private Records
- Find the Allow private records setting
- Toggle the switch on or off
- Changes save automatically
API Settings
API Access
Modules are accessible via the Coherence API using their slug:
GET /api/v1/modules/{module-slug}/records
POST /api/v1/modules/{module-slug}/records
For API documentation and authentication, see API Overview.
API Name
The slug serves as the API name. To use a different identifier in API calls, you'll need to change the slug.
Module Types
The Advanced tab may display the module's type:
| Type | Description |
|---|---|
| Workspace | Custom module created by your workspace |
| System | Built-in Coherence module |
| Vendor | Managed by Coherence or a partner |
Vendor modules have restricted editing. Core functionality is maintained by Coherence, though you can often customize fields and views.
Best Practices
Naming Conventions
Establish consistent naming across your workspace:
- Core modules: People, Accounts, Deals, Leads
- Operations: Projects, Tasks, Milestones
- Industry-specific: Properties, Candidates, Patients
Slug Planning
Choose slugs carefully since changing them later breaks links:
- Use descriptive, short slugs
- Consider future API integrations
- Avoid abbreviations that may be unclear
Record Privacy
Only enable private records when you have a clear use case:
- Personal notes
- Draft records before publishing
- Confidential employee data
For most collaborative modules, keep records shared by default.
Troubleshooting
"Slug already exists"
Another module is using this slug. Each slug must be unique. Choose a different identifier.
"Cannot change slug for vendor module"
Vendor-managed modules have locked slugs. Contact Coherence support if you need to change the identifier.
"Invalid slug format"
Check that your slug:
- Starts with a letter (not a number)
- Uses only lowercase letters, numbers, and hyphens
- Contains no spaces or special characters
Related: Module Builder Guide | API Overview