Common Questions

You need an Org Loom account and the sign-in details for the Salesforce user you want to connect. The first connection to an org may also need a Salesforce administrator to install the managed package, confirm its OAuth policy, and assign the Org Loom permission set.

Use Production / Developer Edition for standard production sign-in, Sandbox for a sandbox, and Custom URL when your org requires its own My Domain or you are connecting a scratch org. For a custom connection, use the org’s Current My Domain URL, not a record or Setup page URL.

The managed package provides the Salesforce-side services Org Loom uses for saved canvases, activity records, and canvas encryption. Its permission set lets your user call those package services. It does not grant access to your Salesforce business objects or fields.

Yes. Open the Salesforce control in the top-right area of the canvas to add another connection or switch the active org. Switching does not upload anything, and the current canvas stays open so you can review it against the selected connection.

No. Creating drafts, editing cards, drawing relationships, importing onto the canvas, and using canvas tools only change the staged canvas. Salesforce records change only after you choose Upload to Salesforce and confirm.

Use Browse records for point-and-click filters, Import via SOQL for a precise query, or Import CSV when the rows already live in a file. Each path gives you a review step before records are added to the canvas.

Browse recordsImport with SOQLImport a CSV

Import the files onto the canvas, review direct Salesforce field mappings under Columns, and configure any reference-only keys under Relationships. Inspect the resulting cards, make any needed changes, then choose Upload to Salesforce. For very large jobs that do not need canvas review, use Salesforce Data Loader.

Add the parent and child cards, then draw a relationship between them. If more than one lookup could connect the objects, Org Loom asks which field to use. During upload, new parents are created first and their Salesforce IDs are applied to the related children.

For a multi-file CSV import, use a separate reference column such as AccountNameKey. Mark it as Match to a related record in another CSV - not uploaded, then use Relationships to choose the target column to match and the Salesforce lookup to populate.

Connect records on a canvasConnect rows from CSV files

Use Bulk edit to set or replace values across a selection, Auto-fill to populate empty fields, Find duplicates to review likely duplicate cards, and Diff records to compare two records field by field. These tools change only the canvas and support review or undo before upload.

Bulk edit recordsFill empty fieldsFind duplicates

Save preserves the canvas layout, cards, relationships, and staged work as an encrypted file in your Salesforce org. It does not change the business records on the canvas. Upload to Salesforce creates, updates, or deletes those business records.

The upload review checks the records for missing required values, incompatible field values, relationship problems, and validation issues Org Loom can determine in advance. Salesforce remains the final authority and still applies permissions, validation rules, duplicate rules, flows, triggers, and other automation.

Review the result before retrying. Successful rows have already changed Salesforce, while failed rows remain available for correction. Fix the reported problem and retry only the failed work. Re-uploading a complete insert file can create duplicates of rows that already succeeded.

Yes. Map a CSV column to Salesforce ID (Id), and Org Loom automatically loads records whose IDs exist while treating blank IDs as drafts. If you map an eligible Salesforce External ID field, the Upsert by external id operation becomes available. Review the resulting records on the canvas before uploading changes to Salesforce.

Recall can move records created by an Org Loom upload to the Salesforce Recycle Bin and can restore selected fields on updated records when the earlier values are available. It protects later changes by excluding them by default, and it cannot undo every automation side effect or restore records deleted by the original upload.

Save the canvas, choose Share, select a Salesforce user, and assign a role. Viewers can inspect the canvas, Contributors can fill assigned slots, and Editors can change and save the shared canvas. The owner can change or revoke access later.

Mark the fields as slots, add instructions if needed, then share the saved canvas with the person as a Contributor. The contributor can fill the assigned slots while the rest of the canvas remains read-only.

Org Loom stops the later save when the stored canvas changed after that person opened it. The person can load the newer Salesforce version, deliberately save their version anyway, or cancel and preserve their current work while deciding.

A Team workspace admin controls which member actions are allowed, including browsing, SOQL import, bulk edit, upload, refresh, sharing, Recall, and AI features. Salesforce permissions still apply after the workspace permission is granted, so both layers may need to be checked.

Yes. A Team admin can require approval for production-org actions. A member requests access when a protected action is blocked, the admin reviews the org and user, and the member retries after approval. Sandbox work is not treated as a production approval request.

Prepare the source records on a canvas, choose Migrate to another org, connect the destination, and work through the guided review. You decide what happens to each record, resolve schema differences, review the final plan, and then upload to the destination.

Create new is the default for each migrated record. Choose Update existing when the source record represents a destination record that already exists, then review or select the destination match. You can change the match field only for records you intend to update.

The migration review identifies source fields the destination connection cannot use. You can map a source field to a compatible destination field or drop that source value from the migration. Dropping it does not delete destination data. Relationships are preserved when the related records and a compatible destination lookup are available.

Resolve destination differencesReview migrated relationships

Org Loom sends Anthropic your prompt and the selected Salesforce object and field schema. Existing canvas record values are not automatically included. Any record data you type into the prompt is part of the request and is sent.

No. Generate with AI proposes new draft records for the selected object types. It does not update records already on the canvas, and applying the proposal still changes only the canvas. Salesforce changes only if you later review and confirm an upload.

Yes. A member with AI client access can generate a personal token for a compatible MCP client. The token represents only the user who generated it and is limited to the active workspace. The client and model provider you choose receive the information exposed by the Org Loom tools you approve and the actions you ask the client to perform.

Org Loom shows warnings as the workspace approaches its included allowance. When the allowance is exhausted, built-in AI generation pauses until the allowance resets or the workspace buys additional AI credits. Workspace admins can review the current allowance and AI activity.

An active canvas and unsaved changes stay in the browser tab, including tab-scoped session storage used for recovery. While a saved canvas is actively shared, bounded synchronization state is also held temporarily in server memory. Saved canvases and submitted teammate responses are encrypted and stored in your Salesforce org. Salesforce record field values are processed temporarily and are not stored in Org Loom’s application database.

No. Org Loom acts as the connected Salesforce user. Object permissions, field-level security, record sharing, and Salesforce automation remain in control. Workspace roles and permissions can limit a user further, but they cannot grant Salesforce access the connected user does not have.

Activity History records minimized operation metadata such as the actor, action, time, status, and relevant counts. It does not store Salesforce field values and is not a compliance-grade audit log. Use Salesforce’s native record history when you need authoritative confirmation of record-level changes.

Pro is designed for one person and includes the core canvas features. Team adds a multi-member workspace, member roles and permissions, shared administration, production-org approval, and workspace-level controls. Choose Team when the work or the governance needs to span more than one person.

Open Workspace from the canvas, choose the workspace, and open its Billing tab. The workspace owner can review the plan, open the billing portal, and change the Team seat quantity. Billing belongs to the workspace, not to an individual Salesforce connection.