Appearance
View Actions
View Actions are the interactive buttons that appear in your custom views. They let you add powerful functionality to your tables and records, giving users quick access to common tasks and workflows.
What are View Actions?
View Actions are custom buttons that you can add to your tables and records. Each action represents a specific task or operation that users can perform with a single click.
Think of them as shortcuts to common workflows - instead of navigating through multiple screens, users can accomplish tasks directly from where they're working.
Types of Actions
Primary Actions
Blue buttons for your most important actions
Use primary actions for the main tasks users perform most often:
- Export data
- Generate reports
- Create new records
- Start workflows
Primary actions stand out visually and draw attention to key functionality.
Secondary Actions
Gray buttons for supporting tasks
Use secondary actions for helpful but less critical tasks:
- View details
- Copy links
- Open related records
- Access settings
Secondary actions provide useful functionality without overwhelming the interface.
Destructive Actions
Red buttons for dangerous operations
Use destructive actions for operations that delete, remove, or permanently change data:
- Delete records
- Reset data
- Clear selections
- Remove associations
The red styling warns users that these actions have serious consequences.
Outline Actions
Subtle buttons for neutral operations
Use outline actions for toggles, filters, and neutral operations:
- Toggle views
- Apply filters
- Switch modes
- Show/hide elements
Outline actions are visually quiet and work well for utility functions.
Action Styles
Regular Buttons
Actions with labels show both an icon (optional) and descriptive text:
[📊 Generate Report] [📤 Export Data] [🗑️ Delete Selected]Regular buttons are clear and self-explanatory, perfect when you have space and want maximum clarity.
Icon-Only Buttons
Actions without labels show only an icon in a compact square button:
[⚙️] [📋] [🔍]Icon-only buttons save space and work well in toolbars or when you have many actions. Make sure the icons are intuitive!
Where Actions Appear
Table Actions (List Views)
Actions appear in your table toolbar, alongside standard buttons like Filter and New:
Users Table
[Filter] [New User] [📊 Generate Report] [📤 Export Users] [✉️ Send Emails]Table actions typically work with multiple records or the entire dataset.
Record Actions (Record Views)
Actions appear in individual record headers, alongside Update and Delete:
John Smith - User Record
[Edit] [Delete] [✉️ Send Welcome] [📋 Copy Profile] [🔄 Reset Password]Record actions work with the specific record you're viewing.
Dashboard Actions (Dashboard Views)
Actions appear in dashboard contexts for overview and analytics:
Sales Dashboard
[📊 Refresh Data] [📈 Generate Report] [📤 Export Summary]Dashboard actions typically provide high-level operations and insights.
Planning Your Actions
Start with User Needs
Ask yourself:
- What tasks do users perform most often?
- What workflows require multiple steps that could be simplified?
- What external integrations would be helpful?
- What reports or exports do users need?
Keep It Simple
- Limit actions per view: 3-7 actions work best
- Use clear names: "Export Users" is better than "Export"
- Group related actions: Put similar actions together
- Consider frequency: Put most-used actions first
Choose the Right Type
- Primary: Your #1 most important action
- Secondary: Helpful supporting actions
- Destructive: Anything that deletes or resets
- Outline: Toggles, filters, and utilities
Action Examples
User Management Table
[👥 Bulk Update] - Primary: Most common admin task
[📤 Export CSV] - Secondary: Useful for reporting
[✉️ Send Emails] - Secondary: Communication tool
[🗑️ Delete Selected] - Destructive: Dangerous operation
[🔍] - Outline: Search toggle (icon-only)Order Record
[📧 Send Invoice] - Primary: Key business process
[📦 Track Shipment] - Secondary: Customer service
[📋 Duplicate] - Secondary: Efficiency tool
[💰 Process Refund] - Destructive: Financial impact
[⚙️] - Outline: Settings (icon-only)Sales Dashboard
[📊 Refresh Data] - Primary: Keep data current
[📈 Generate Report] - Secondary: Analysis tool
[📤 Export Summary] - Secondary: Sharing tool
[🔄] - Outline: Auto-refresh toggleBest Practices
Naming Actions
- Be specific: "Export Users" not "Export"
- Use action words: "Generate", "Send", "Create", "Delete"
- Match user language: Use terms your users understand
- Keep it short: 1-3 words when possible
Choosing Icons
- Use familiar icons: Stick to common symbols users recognize
- Match the action: Trash for delete, download for export
- Be consistent: Use the same icon for similar actions across tables
- Test with users: Make sure icons are intuitive
Organizing Actions
- Most important first: Put primary actions on the left
- Group by type: Keep related actions together
- Separate dangerous actions: Put destructive actions at the end
- Use consistent ordering: Same pattern across all tables
User Experience
- Provide feedback: Show success/error messages after actions
- Confirm dangerous actions: Ask "Are you sure?" for destructive operations
- Handle permissions: Only show actions users can actually perform
- Consider mobile: Make sure actions work on smaller screens
Common Use Cases
Data Management
- Export to CSV/Excel
- Bulk update records
- Import from files
- Sync with external systems
Communication
- Send emails to users
- Generate and send reports
- Create notifications
- Share records with others
Workflow Automation
- Approve/reject items
- Move records through stages
- Trigger external processes
- Update related records
Analysis & Reporting
- Generate custom reports
- Create data visualizations
- Export analytics data
- Schedule automated reports
Getting Started
- Identify your users' most common tasks
- Start with 2-3 essential actions
- Choose clear, descriptive names
- Pick appropriate action types and icons
- Test with real users
- Add more actions based on feedback
Remember: Great view actions feel like natural extensions of your workflow. They should make common tasks faster and easier, not add complexity to your interface.
Related Documentation
- Custom Views - Learn about creating and managing custom views