Skip to main content

History and Logging

SimplePerm records every migration you run. Here's how the tracking and logging system works.

Migration Projects​

Each migration run creates a Migration Project record (stored as Migration_Project__c) that captures:

  • Status -- Queued, Running, Success, Partial Success, or Failed
  • Source Profile -- The profile name(s) that were migrated
  • Started At -- When the migration kicked off
  • Completed At -- When the migration finished
  • Error Message -- If something went wrong, the details are stored here

Think of a Migration Project as the top-level container for a single migration run.

Migration Logs​

Each pipeline step generates one or more Migration Log records (stored as Migration_Log__c), linked to the parent Migration Project. Logged steps include:

  • Profile Retrieval -- Reading profile metadata from your org
  • Permission Parsing -- Parsing raw metadata into structured permissions
  • Permission Set Building -- Constructing the new permission set definition
  • Deployment -- Deploying the permission set via the Metadata API
  • Verification -- Confirming the deployed permission set matches expectations
  • User Assignment -- Assigning the new permission set to users (if you chose this option)

Each log entry records the step name, a message describing what happened, and a log level.

Log Levels​

Log entries use three levels:

  • Info -- Normal operations. Most entries are Info-level, confirming steps completed as expected.
  • Warning -- Something non-critical happened. For example, a permission type had fewer entries than expected, but the migration still completed.
  • Error -- A failure. The log message explains what went wrong and which step failed.

In the History tab, toggle Show Detailed Logs to see verbose per-permission entries. These include individual field-level and object-level permission details, hidden by default to keep the view manageable.

Viewing History​

Open the History tab in the SimplePerm app. You'll see a table of recent migrations, each showing:

  • The source profile name
  • A status badge: green for Success, yellow for Partial Success, red for Failed
  • Timestamps for when the migration started and finished

Click any record to expand it and view the full log trail. Logs appear in pipeline step order, so you can follow the migration from start to finish.

Data Retention​

Migration Project and Migration Log records persist until you manually delete them. There's no automatic purge for completed migrations.

Deleting a Migration Project also deletes all its Migration Log records -- they're linked by a master-detail relationship, so the cascade is automatic.

Draft migration projects (migrations that were started but never completed) are cleaned up automatically after 30 days by a scheduled job.