Permissions and Access Requirements
Overview
This guide provides comprehensive information about permissions and access requirements for Out of Office Assistant. Understanding these permissions is essential for proper deployment, user management, and security configuration.
Permission Architecture
Out of Office Assistant operates within Jira Cloud’s permission framework and adds its own app-specific permissions for advanced functionality.
Core Permission Levels
The app recognises five primary user roles with distinct capabilities:
Role | Permissions Required | Capabilities |
|---|---|---|
End User | Browse Projects | Create personal rules and Templates, view own rules, set up own integrations |
Out of Office Admins | Browse Projects | Same as End User + can create Rules and Templates on behalf of other users |
Project Admin | Project Administration | Manage rules for project members, can create Rules and Templates on behalf of Project Members, perfect for Team Leads |
Jira Admin | System Administration | Global settings, user administration, edit all integrations after initial User Setups |
Service Desk Agent | Agent access to JSM projects | Create personal rules and Templates, view own rules, set up own integrations, Approval delegation |
User Role Permissions Matrix
End User Permissions
Jira Requirements:
Browse Projects permission (minimum required)
Access to projects where rules will be applied
User account in good standing
Out of Office Assistant Capabilities:
✅ Create personal rules - Set up absence rules for their own account
✅ Manage own rules - Edit, disable, and delete personal absence rules
✅ View own rule status - Monitor rule activation and effectiveness
✅ Basic integration setup - Configure personal Integrations and Slack connections
✅ Self-service troubleshooting - Access basic rule diagnostics
Restrictions:
❌ Cannot view other users’ rules
❌ Cannot create rules for other users
❌ Cannot access administrative functions
❌ Cannot configure global settings
Out of Office Admin Permission
(can be used for HR Team members)
Jira Requirements:
Browse Projects permission
Project visibility for all projects
Out of Office Assistant Capabilities:
✅ All End User capabilities
✅ User absence visibility + rule management - Create and manage rules for all Users
Restrictions:
❌ Cannot access global administrative functions
❌ Cannot configure system-wide settings
Project Administrator Permissions
Jira Requirements:
Project Administration permission for relevant projects
Manage Users permission within projects
Access to project configuration areas
Out of Office Assistant Capabilities:
✅ All End User capabilities
✅ Team absence visibility + Project-level rule management - Create and manage rules for project members
Access Locations:
Main Out of Office Assistant interface
Project settings integration (where available)
User Administration interface (project-filtered view)
Jira Administrator Permissions
Jira Requirements:
Jira Administrator global permission
System Administration access
Manage Apps permission
Out of Office Assistant Capabilities:
✅ All Project Administrator capabilities
✅ Global system configuration - Access to Global Settings
✅ Complete user administration - Manage all users across all projects
✅ Integration management - Configure system-wide integrations
✅ REST API permissions - Manage API tokens and access
✅ App installation and configuration - Install, configure, and manage the app
Administrative Interface Access:
Primary Location: Apps → Out-Of-Office Assistant → User Administration
Service Desk Agent Permissions
Jira Requirements:
Agent access to Jira Service Management projects
Customer interaction permissions
Approval workflow participation rights
Out of Office Assistant Capabilities:
✅ All End User capabilities
✅ Approval delegation - Set up approval coverers for customer requests
✅ Customer communication - Maintain service quality during absences
✅ Service availability indicators - Display absence status to customers
Administrative Interface Permissions
User Administration Access
Location: Apps → Out-Of-Office Assistant → User Administration
Access Requirements:
Jira Administrator permission required for full access
Project Administrator & Out of Office Administrator may have filtered access to project users only
Standard users cannot access this interface
Interface Capabilities:
Users Tab: Complete user management and rule oversight
REST API Permissions Tab: API token management and external access control (Admin only)
Global Settings Button: System-wide configuration (Admin only)
REST API Permissions Management
Location: User Administration → REST API Permissions tab
Access Requirements:
Jira Administrator permission required
System administration rights necessary for token creation
Token Management Features:
Create New Token: Generate API access tokens for external integrations
User Assignment: Link tokens to specific user accounts
Scope Configuration: Define token access permissions and limitations
Access Monitoring: Track token usage and last access times
Integration Permissions
Calendar Integration Requirements
Microsoft Outlook:
User Level: Personal Microsoft 365 account or organizational account
Permissions Needed:
Scopes:
'User.Read'
'MailboxSettings.Read'
'offline_access'
Google Workspace Calendar:
User Level: Google Workspace account
Permissions Needed:
Slack Integration Requirements
Individual Setup:
User Level: Access to Slack workspace where integration will be installed
Permissions Needed: Ability to add apps to Slack workspace
Workspace-Wide Deployment:
Admin Level: Slack workspace administrator permissions
Requirements: Organizational approval for third-party app integration
Tempo Integration Requirements
API Access:
Admin Level: Tempo administrator permissions for API token generation
User Level: Access to Tempo timesheets and planning features
Requirements: Valid Tempo subscription and configuration
Best Practices for Permission Management
Organizational Deployment
Staged Rollout Approach
Phase 1: Pilot Group
Select small group of end users
Test basic functionality and permissions
Identify and resolve permission issues
Phase 2: Team Leads and Project Admins
Add management layer users
Configure project-level permissions
Test administrative functions
Phase 3: Organization-Wide
Deploy to all eligible users
Monitor for permission-related support tickets
Optimize permission schemes based on usage patterns
Support
Permission Support Process
Level 1: User Self-Service
Provide Quick Start Guide for basic setup
Reference this permissions guide for detailed requirements
Level 2: Project Administrator
Assist with project-level permission configuration
Help resolve user access issues within projects
Coordinate with Jira Administrators as needed
Level 3: Jira Administrator
Resolve system-wide permission issues
Configure global settings and administrative access
Manage API tokens and integration permissions
Level 4: Resolution Support
Contact for app-specific permission issues
Escalate complex integration permission problems
Report suspected permission bugs or security concerns
Contact Information
Resolution Support Portal: resolution.atlassian.net/servicedesk
Documentation: wiki.resolution.de
Community: Atlassian Community forums for peer support
Permissions Status: ✅ COMPLETE
Next Step: Quick Start Guide for new user onboarding