Skip to main content
Back to Blog
permissions roles security access

User Roles and Permissions

Swifty Team Jan 8, 2025 2 min read

Not everyone in your business should see everything. A sales rep doesn't need access to payroll data. A customer service agent shouldn't be able to delete invoices. A partner portal user should only see their own records.

These aren't edge cases — they're the everyday reality of running a team.

Roles That Reflect Reality

Swifty's permission system is built around roles. Each role defines what a user can do: which objects they can view, which they can edit, which they can create and delete.

Roles are defined by you, named after your real organizational structure: Administrator, Sales Manager, Sales Rep, Support Agent, Finance, Read-Only. Whatever makes sense for your team.

Assign a role to a user, and they immediately get the right access — no individual permission-setting for each person.

Field-Level Control

Most permission systems stop at the record level: you can see this type of record, or you can't. Swifty goes further.

Field-level permissions let you show or hide specific fields based on role. A cost price field might be visible to managers but hidden from frontline staff. An internal notes field might only appear for the support team. A confidential status might be readable by some roles and editable only by others.

The form and detail page adapt automatically based on who's logged in. No custom views required.

Scope and Ownership

Permissions in Swifty also work with ownership. You can configure roles so users only see records they created, or records assigned to them, or records belonging to their team. This makes it straightforward to build multi-tenant views or territory-based access without complex logic.

Security That Isn't a Burden

The goal of a good permission system isn't just restriction — it's clarity. When team members see a clean interface with only the options relevant to their role, they work faster. There's less clutter, fewer mistakes, and no confusion about what they should or shouldn't be doing.

Security and usability aren't opposites. In a well-designed permission system, they reinforce each other.

Related posts

Composed Data Sources

Chain and relate data sources for rich dashboards — compose complex data views from simpler sources without writing code.

Computed Expressions

Transform data with template expressions and built-in functions — format, combine, and derive values from your data without code.

Cross-Source Data Joins

Combine data from multiple sources in one view — join records from your database with data from external services using a shared key.