Access Request Intent
Updated
by
Stephen Boss
Access Request Intent
The Access Request intent streamlines the handling of IT service requests for granting access to systems, applications, or resources within an organization. This intent automates triage, collects necessary details, and enables your Magic Agents to handle threads efficiently, whether the request is for the user themselves or on behalf of someone else.
Example Use Cases:
- Granting access to shared drives, folders, or cloud resources.
- Providing permissions to enterprise applications or internal systems.
- Temporary access to restricted areas or tools for specific projects.
Key Features
- Automated Triage: Quickly collect key information like user details, requested access, and justification to initiate workflows.
- Workflow Enablement: Suggest standard resolutions or escalate the request to appropriate teams for further action.
- Secure Processes: Ensure clear documentation of access requests and reasons for tracking and auditing purposes.
Configuration Guide
1. Create the Intent
To create the Access Request Intent, follow these steps:
- Navigate to Thread Admin (https://admin.getthread.com) > Magic AI > Agent > Catalog (Direct Link).
- Click Create Intent.
- Input the intent details:
- Intent Name: "Access Request" (customizable to match your workflow needs).
- Description: "A request to grant access to a specific system, application, or resource within the organization, either for oneself or on behalf of another user."
- Who can use this intent: Set it to "All clients," or adjust to specific client types if necessary.
2. Configure Arguments
Define the fields required to triage and process access requests. Use the specifications exactly as shown in the images:
Field Name | Description | Type | Required |
Full Name | Ask the name of the user they are requesting access for, if the user is asking for themselves, don't ask, use their name. | Textfield | Yes |
Ask the email of the user they are requesting access for, if the user is asking for themselves, don't ask, use their email. | Email address | Yes | |
Resource Name | Ask the system, application, or resource access is needed for. If the user has already provided this information, don't ask. | Textfield | Yes |
Level of Access | Ask the level of access that is needed. If the user has already provided this information, don't ask.
Try to provide up to 3 examples of the level of access available to request, based on the system, application or resource the user is asking for access to. | Textfield | Yes |
Reason for Access | Ask why access to this resource is needed. If the user has already provided justification, use the justification already provided and don't ask this question. | Textfield | Yes |
Additional Details | Provide space for additional details or special instructions, if any. | Textfield | No |
3. Configure External Reply (Optional)
Set up an external reply to confirm receipt of the access request. For example:
"Your access request has been received. You’ll be notified when the request has been reviewed or approved."
For denied requests, write a prompt to:
- Notify the requester of the denial.
- Explain the reason for the denial.
- Provide guidance on how to submit additional information or escalate the request.
Note: Approval workflows for denied requests are coming soon.
4. Add Automation (Optional)
Enhance the intent with automation to streamline workflows:
- Route Requests: Automatically assign the request to the appropriate IT or access management team based on the resource or access level.
- Integrate RPA Platforms: Pass the access request payload into any RPA (Robotic Process Automation) platform that supports incoming webhooks. This allows you to automate granting access once approval is provided.
FAQs and Troubleshooting
Customization Tips
- Pre-Filled Fields: Use data from previous interactions to pre-fill known information like user name and email, reducing manual input.
- Dropdown Options for Access Levels: Replace free-text entry with predefined options (e.g., Viewer, Editor, Admin) to minimize errors.
Can access requests include attachments?
Yes, you can process attachments by adding a dedicated argument to handle file uploads. This allows users to include necessary documents directly within their access request. Additionally, image processing capabilities for Magic Agents are coming soon, enabling agents to interpret images sent with requests for even more streamlined workflows.
How are denied requests handled?
In the external reply section, write a prompt to notify the requester of the denial. Use this prompt to explain the reason for the denial and provide instructions on how to submit additional information or escalate the request. Approval workflows for managing these denials are coming soon.
What if a user requests access to an unknown resource?
Include a dropdown or searchable list of frequently requested resources. Provide an “Other” option for unlisted resources.
How can I ensure compliance with access policies?
Integrate approval steps (coming soon) and add validation logic to ensure the request complies with internal policies before proceeding.
