Remove User Access from Pirsch | OpsBlu Docs

Remove User Access from Pirsch

Remove user access in Pirsch — revoke permissions, deactivate accounts, and maintain security audit trails.

Removing Team Members from Pirsch

Removing user access from Pirsch is essential for maintaining security and managing team changes. This guide covers when and how to revoke access to your analytics account.

When to Remove Access

Employee Offboarding

Remove access when:

  • Employees resign or are terminated
  • Team members transfer to different departments
  • Role changes eliminate analytics needs
  • During organizational restructuring

Contractor Completion

Revoke access when:

  • Project contracts are completed
  • Freelancer engagements end
  • Temporary assignments finish
  • Consulting relationships conclude

Security and Compliance

Remove access if:

  • Unauthorized access is suspected
  • Email accounts are compromised
  • Security audits identify unnecessary access
  • During access cleanup initiatives

Inactive Users

Regularly remove:

  • Users who haven't logged in for 90+ days
  • Duplicate accounts
  • Test accounts from implementation
  • Former employees missed during offboarding

Prerequisites

Before removing team members:

  • Verify you have Owner role privileges
  • Identify the correct user to remove
  • Document the reason for removal
  • Ensure no dependencies on their access

Step-by-Step Instructions

Step 1: Navigate to Team Settings

  1. Log in to your Pirsch account at pirsch.io
  2. Click Settings in the navigation menu
  3. Select "Team" or "Team Members"
  4. View the list of current team members

Step 2: Locate the User

  1. Find the team member in the list
  2. Verify you're removing the correct person (check email)
  3. Note their current role
  4. Check their last login date if available

Step 3: Initiate Removal

  1. Click the remove, delete, or trash icon next to their name
  2. A confirmation dialog will appear

Step 4: Confirm Removal

The confirmation shows:

  • User's email address
  • Current role
  • Warning that access will be immediately revoked

Actions:

  1. Read the confirmation carefully
  2. Verify you're removing the intended person
  3. Click "Remove" or "Confirm" to proceed
  4. Click "Cancel" if you selected the wrong user

Step 5: Verify Removal

After confirmation:

  1. Success message appears
  2. User disappears from team member list
  3. Access is immediately revoked
  4. Any active sessions are terminated

What Happens After Removal

Immediate Effects

  • Access is revoked instantly
  • User cannot log in to the account
  • Active browser sessions are invalidated
  • User stops receiving account notifications

Data Preservation

  • Historical analytics data remains intact
  • No analytics data is deleted
  • Past contributions are preserved
  • Removal only affects future access

Common Use Cases

Employee Departure

When employees leave:

  1. Include Pirsch in offboarding checklist
  2. Remove access on last day or immediately upon termination
  3. Document removal date for records
  4. Verify removal was successful

Contractor Project End

When contracts complete:

  1. Schedule removal for contract end date
  2. Notify contractor in advance
  3. Remove access promptly
  4. Document for contract records

Security Incidents

For security concerns:

  1. Remove access immediately
  2. Document the incident
  3. Notify IT security team
  4. Review what data was accessed

Access Cleanup

During regular audits:

  1. Generate list of inactive users
  2. Verify employment status
  3. Remove all confirmed departed employees
  4. Document cleanup actions

Best Practices

Security

  1. Immediate Removal: Don't delay removing departed employees
  2. Verify Identity: Confirm you're removing the correct person
  3. Audit Trail: Document all removals with date and reason
  4. Regular Reviews: Conduct quarterly access reviews

Communication

  1. Stakeholder Notification: Inform team leads of removals
  2. Contractor Communication: Give advance notice when possible
  3. Documentation: Update access records promptly
  4. Team Coordination: Notify teams of significant removals

Process

  1. Offboarding Checklist: Include Pirsch in standard procedures
  2. Calendar Reminders: Set removal dates for contractors
  3. Access Documentation: Maintain records of who has access
  4. Verification: Confirm successful removal

Troubleshooting

Cannot Remove a User

If unable to remove someone:

  1. Verify you have Owner permissions
  2. Cannot remove yourself as Owner
  3. Cannot remove the last Owner
  4. Contact Pirsch support for assistance

User Can Still Access

If removed user reports continued access:

  1. Ask them to clear browser cache and cookies
  2. They may have multiple devices logged in
  3. Verify removal in team settings
  4. They might be accessing a different account
  5. Contact Pirsch support if issue persists

Accidentally Removed Wrong Person

If you removed the wrong team member:

  1. Immediately re-invite them with original role
  2. Inform them of the mistake
  3. Verify they can access again
  4. Implement verification to prevent recurrence

Need to Remove Multiple Users

To remove several members:

  1. Remove each user individually
  2. Work systematically through the list
  3. Verify each removal before proceeding
  4. Document all removals

After Removing Access

Verification

After removal:

  1. Refresh team settings page
  2. Confirm user no longer appears in list
  3. Document removal in access records
  4. Notify relevant stakeholders

Follow-Up

Complete after removal:

  1. Update internal documentation
  2. Inform relevant managers
  3. Note availability for new team members
  4. Archive related communications

Security Verification

For sensitive removals:

  1. Review recent activity if available
  2. Document for security records
  3. Ensure removal from related systems
  4. Monitor for unusual activity
Back to top