Configuración / Autorización
Primeros pasos
Tickets y conversaciones
Herramientas de agente
Automatización y flujos de trabajo
Correo y notificaciones
Extensibilidad
Authorization
The configuration keys, routes, gates, and commands shown here describe the Laravel adapter unless a framework is named. Use your adapter source for its corresponding API and defaults.
Escalated uses two authorization gates to control access to agent and admin views. Define these in your application to control who can manage tickets.
Note: Escalated automatically shares
page.props.escalatedto all Inertia responses, containing the route prefix and the current user's agent/admin status.
Granular permissions
Escalated ships with 52 granular permissions organized into logical groups:
| Group | Example permissions |
|---|---|
| Tickets | tickets.view, tickets.create, tickets.update, tickets.delete, tickets.merge, tickets.assign, tickets.change_department |
| Conversations | conversations.reply, conversations.add_note, conversations.delete, conversations.edit |
| Users | users.view, users.create, users.update, users.delete, users.impersonate |
| Knowledge Base | kb.view, kb.create, kb.update, kb.delete, kb.publish |
| Reports | reports.view, reports.export, reports.scheduled |
| Admin | admin.settings, admin.departments, admin.sla, admin.macros, admin.automations, admin.roles, admin.integrations, admin.billing |
| Bulk Operations | bulk.update, bulk.delete, bulk.assign |
| Tags | tags.view, tags.create, tags.delete |
| SLA | sla.view, sla.manage, sla.override |
| Satisfaction | satisfaction.view, satisfaction.manage |
| Collaboration | collaboration.side_conversations, collaboration.followers, collaboration.shared_views |
Each permission can be granted or denied independently per role.
Default roles
Escalated includes three built-in roles:
Admin
Full access to all 52 permissions. Admins can manage settings, roles, agents, departments, SLA policies, automations, and billing. Cannot be deleted.
Agent
Standard support agent with permissions to manage tickets, conversations, and the knowledge base. Cannot access admin-level settings, roles, or billing.
- Tickets: view, create, update, assign
- Conversations: reply, add note
- Knowledge Base: view, create, update
- Tags: view, create
- Reports: view
- Collaboration: side conversations, followers
Light Agent
Restricted role for part-time or external collaborators. Light agents can view tickets and add internal notes but cannot send public replies or modify ticket properties.
- Tickets: view
- Conversations: add note
- Knowledge Base: view
- Tags: view
Custom roles
Create custom roles from Admin -> Roles to match your team's structure. Each custom role starts with no permissions -- toggle individual permissions on or off using the permission matrix.
Creating a custom role
- Navigate to Admin -> Roles
- Click New Role
- Enter a role name and optional description
- Use the permission matrix to enable or disable each of the 52 permissions
- Click Save
Assign the role to agents from the agent profile page or during agent creation.
Permission matrix UI
The permission matrix is a grid that shows all permissions grouped by category. Each row is a permission and each column is a role. Toggle a cell to grant or revoke that permission for the role. Changes take effect immediately after saving -- no agent restart is required.
Define dos gates en App\Providers\AppServiceProvider::boot() para Laravel 12+, o en App\Providers\AuthServiceProvider::boot() para Laravel 11 y anteriores:
use Illuminate\Support\Facades\Gate;
// Quien puede acceder al panel de agentes y gestionar tickets
Gate::define('escalated-agent', fn ($user) =>
$user->is_agent
);
// Quien puede acceder a la configuracion de administracion (departamentos, SLAs, reglas, etc.)
Gate::define('escalated-admin', fn ($user) =>
$user->is_admin
);
Los nombres de los gates son configurables a traves de config/escalated.php bajo authorization.admin_gate y authorization.agent_gate.
Configura lambdas en el inicializador:
Escalated.configure do |config|
config.admin_check = ->(user) { user.admin? }
config.agent_check = ->(user) { user.agent? || user.admin? }
end
Define callables en tu configuracion:
ESCALATED = {
"ADMIN_CHECK": lambda user: user.is_staff,
"AGENT_CHECK": lambda user: hasattr(user, "is_agent") and user.is_agent,
}
Configura los callbacks de autorizacion en tu configuracion:
authorization: {
isAgent: async (user) => {
return user.role === 'agent' || user.role === 'admin'
},
isAdmin: async (user) => {
return user.role === 'admin'
},
}
Define dos gates de Laravel, luego haz referencia a ellos en el plugin de Filament:
Gate::define('escalated-agent', fn ($user) => $user->is_agent);
Gate::define('escalated-admin', fn ($user) => $user->is_admin);
EscalatedFilamentPlugin::make()
->agentGate('escalated-agent')
->adminGate('escalated-admin')
WordPress utiliza roles y capacidades integrados. El plugin registra dos roles personalizados:
| Rol | Descripcion |
|---|---|
escalated_agent |
Puede ver y gestionar tickets |
escalated_admin |
Acceso completo a configuracion, departamentos y politicas SLA |
Authorization is handled entirely server-side. The Flutter package sends a Bearer token with each request, and your backend API controls what the authenticated user can access.
There are no client-side gates to define — the mobile app is a customer-facing UI, so agent and admin authorization checks only apply on the web.
Checking Auth State
Use the authProvider to check whether the current user is authenticated:
final authState = ref.watch(authProvider);
if (authState.isAuthenticated) {
// User is logged in, show ticket list
} else {
// Show login screen
}
Note: The
escalated-agentandescalated-admingates from your backend still apply to all API requests. The mobile app simply doesn't expose agent or admin views.
Authorization is handled entirely server-side. The React Native package sends a Bearer token with each request, and your backend API controls what the authenticated user can access.
There are no client-side gates to define — the mobile app is a customer-facing UI, so agent and admin authorization checks only apply on the web.
Checking Auth State
Use the useAuth hook to access the current user and authentication status:
import { useAuth } from '@escalated-dev/escalated-react-native';
function ProfileScreen() {
const { user, isAuthenticated } = useAuth();
if (!isAuthenticated) {
return <LoginScreen />;
}
return <Text>Welcome, {user.name}</Text>;
}
Note: The
escalated-agentandescalated-admingates from your backend still apply to all API requests. The mobile app simply doesn't expose agent or admin views.