Remove a specific user from script access control list.
Authentication: JWT token required Authorization: Admin level access required (ADMIN or SUPERADMIN) Purpose: Revoke script access from an individual user
Path Parameters:
- script_id: Script identifier/slug or numeric ID
- user_id: User identifier (numeric ID or email address)
Request: No request body required
Response Schema:
{
"data": {
"script_id": "12345",
"restricted": true,
"allowed_roles": [],
"allowed_users": ["user123"],
"access_type": "user_restricted"
}
}
Behavior:
- Removes user from script's allowed users list
- User immediately loses access to script
- Does not affect other users' access
- Gracefully handles removal of non-existent users
Access Effect:
- User can no longer see script in listings
- User cannot execute script
- Existing executions continue to completion
- User may regain access through role-based permissions
Cleanup Logic:
- If user list becomes empty, user restrictions may be removed
- Script may become unrestricted if no other access controls exist
- Access type is recalculated based on remaining restrictions
Use Cases:
- Remove access when user leaves project
- Revoke access due to security concerns
- Clean up outdated user permissions
- Manage temporary access grants
Error Responses:
- 401 Unauthorized: JWT token required
- 403 Forbidden: Admin privileges required
- 404 Not Found: Script does not exist
- 500 Internal Server Error: Failed to remove user access
delete/api/v1/script/{script_id}/access/users/{user_id}
Path parameters
script_idstring required
Path parameter: script_id
user_idstring required
Path parameter: user_id
Response
Success
object required
Changes
No recorded changes to this endpoint across all 1 revision of this API.