Create, configure, and troubleshoot custom objects in Sanka.
Last updated: May 29, 2026
Custom objects let your workspace manage record types that are not included in Sanka by default. Use them when your team needs to track industry-specific records, project records, assets, properties, inspections, memberships, or another structured process.This guide explains when to use a custom object, how to create one, and what to check before adding it to modules, properties, views, forms, imports, or workflows.
Before creating a custom object
Sanka includes standard objects such as companies, contacts, orders, inventory, invoices, payments, and tasks. Standard object names cannot be changed.Create a custom object when:
The record type is not already covered by a standard object.
The record needs its own properties, views, forms, imports, and associations.
Users need to manage the records from a module in Sanka.
Reports, dashboards, workflows, or actions need to reference the records separately.
Avoid creating a custom object when a standard object with custom properties would be enough. For example, item category should usually be an Item property, not a separate custom object, unless each category needs its own record, owner, associations, history, and workflow.Custom objects may not support every specialized feature available on standard objects, such as quote, invoice, payment, inventory, or document-specific flows. Check the expected workflow before relying on a custom object for operational records.
Review a custom object plan with AI
Ask AI to review the design before creating a new object. This helps prevent duplicate objects, confusing names, and fields that should be properties or associations instead.
Sample prompt
/sanka Review this Sanka custom object plan before creating anything. Show whether a standard object already fits, the object name, stable identifier, required properties, views, forms, associations, module placement, import needs, reports, workflows, permissions, and risks if the object is renamed or deleted later. Do not create or update the object yet.
After the review, confirm the object name, identifier, required properties, module placement, and ownership rules.
Create a custom object
Open Workspace and go to Object Management.
At the bottom of Object Management, click Create Custom Object.
Enter the object name and stable identifier. The identifier is used to keep the custom object consistent across settings, imports, and links, so choose it carefully.
Enter the required information and create the object.
The custom object appears in Object Management.
Add properties, views, and forms
After creating the object, add the properties users need to store data.Click New to add properties, then click Update to apply changes.Then configure forms and views so users can create records and see the right columns. A property may exist but remain invisible until it is added to a form or view.For details, see Property Settings and Views and Forms.
Add the custom object to a module
Users can access a custom object from a module after it is added to the module configuration.Select the object frame in the module, add the custom object, and click Save.The custom object appears inside the module.
Expected behavior
When a custom object is configured correctly:
It appears in Object Management.
It appears in the selected module after module settings are saved.
Users with access can create and view records from the configured views and forms.
Custom properties follow their type, required, unique, and option settings.
Imports, exports, reports, dashboards, actions, and workflows can use the object when those features support it.
Associations can connect custom object records to other object records when configured.
If users cannot see the object, check module placement, permissions, workspace access, and whether the object has views and forms that expose the needed properties.
Troubleshooting
The custom object does not appear in the menu
Check whether the object was added to a module and whether the module was saved. Also check the user's module and workspace permissions.
Users can open the object but cannot create useful records
Check whether properties and forms have been configured. A new custom object starts as a framework and needs properties, views, and forms before it is useful.
A field exists but users cannot see or enter it
Check whether the property has been added to the current view or selected form.
A custom object is duplicated with a standard object
Compare the workflow against standard objects. If the records behave like companies, contacts, orders, invoices, items, tasks, or tickets, consider using the standard object with custom properties instead.
Import, report, or workflow behavior is different from standard objects
Check whether the feature supports the custom object and whether required properties, option values, permissions, and associations are configured. Specialized standard-object flows may not apply to custom objects.
Checkpoints
Before creating or changing a custom object, confirm that the design will not split related data across duplicate objects.
Search Sanka...
Review custom object changes
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
3Reviewed object plan2026/05/10 14:00Property objectConfirmed standard objects did not fit and listed required propertiesClaude / Codex
2Created custom object2026/05/10 14:20Property objectCreated object framework and stable identifierSanka user
1Added object to module2026/05/10 14:35Item moduleAdded custom object to the module menuSanka user
Custom object changes should be checked together with modules, properties, forms, views, associations, permissions, imports, reports, and workflows.
Click New to add properties, then click Update to apply changes.
Then configure forms and views so users can create records and see the right columns. A property may exist but remain invisible until it is added to a form or view.
For details, see Property Settings and Views and Forms.
Select the object frame in the module, add the custom object, and click Save.
The custom object appears inside the module.
