Overview
As team members' roles evolve or organizational needs change, you may need to update user permissions in Kissmetrics. This ensures users have appropriate access levels - not too much (security risk) and not too little (productivity blocker).
This guide covers how to modify user permissions, change access levels, and manage user settings in Kissmetrics.
When to Update User Access
Common Scenarios:
- Employee promoted to manager role (needs Admin access)
- Team member changing departments
- Contractor work completed (downgrade to Read-Only or remove)
- Security audit findings
- Project reassignments
- Temporary elevated access needed
- User reported unable to perform required tasks
Permission Levels Quick Reference
| Level | View Reports | Create Reports | Edit Settings | Manage Users | Manage Billing |
|---|---|---|---|---|---|
| Read-Only | ✓ | ✗ | ✗ | ✗ | ✗ |
| User | ✓ | ✓ | ✗ | ✗ | ✗ |
| Admin | ✓ | ✓ | ✓ | ✓ | ✗ |
| Owner | ✓ | ✓ | ✓ | ✓ | ✓ |
Step-by-Step Instructions
Step 1: Navigate to Team Management
- Log in to your Kissmetrics account
- Click your profile icon in the top-right corner
- Select Settings from the dropdown
- Click Team or Team Members in the left sidebar
Step 2: Locate the User
Find by Scrolling:
- Scroll through the team member list
- Users are typically listed alphabetically
Find by Search (if available):
- Use the search box at the top of the list
- Enter the user's name or email address
Step 3: Access User Settings
Option A: Edit Button
- Find the user in the list
- Click the Edit button or pencil icon next to their name
Option B: User Profile
- Click on the user's name or row
- This opens their profile page
- Click Edit Permissions or Manage Access
Step 4: Change Permission Level
In the edit dialog, locate the Permission or Role dropdown
Select the new permission level:
- Owner
- Admin
- User
- Read-Only
Review the permission changes shown
Step 5: Adjust Additional Settings (If Available)
Project Access:
- Select or deselect projects the user can access
- Useful for multi-project or agency accounts
Feature Permissions:
- Enable/disable specific features
- Control access to sensitive data or advanced features
Email Notifications:
- Configure what notifications the user receives
- Report alerts, team updates, etc.
Step 6: Save Changes
- Review all changes carefully
- Click Save, Update, or Save Changes
- User's access is updated immediately
- User may need to log out and back in to see changes
Permission Change Scenarios
Promoting a User to Admin
When: User needs to manage team members and settings
Steps:
- Go to Settings → Team
- Find the user
- Click Edit
- Change permission from "User" to "Admin"
- Save changes
What Changes:
- Can now manage other users
- Can configure tracking settings
- Can create and modify integrations
- Can access all projects
Downgrading Admin to User
When: Admin responsibilities transferred to another team member
Steps:
- Navigate to the user's settings
- Change permission from "Admin" to "User"
- Confirm the change
- Save
What Changes:
- Loses ability to manage users
- Cannot modify settings
- Can still view and create reports
- Retains access to assigned projects
Temporary Elevated Access
Scenario: User needs temporary Admin access for specific task
Best Practice:
- Grant elevated access (User → Admin)
- Set calendar reminder to downgrade after task completion
- Document the temporary change
- Revert access when task is done
Alternative: If Kissmetrics supports it, use time-limited access controls
Restricting Access During Offboarding
Scenario: Employee leaving but needs Read-Only access for transition
Steps:
- Change permission to Read-Only
- Remove from sensitive projects
- Disable ability to export data (if available)
- Set reminder to fully remove access after transition period
- Monitor access logs during transition
Best Practices
Access Reviews
Quarterly Reviews:
- Export list of all users and their permissions
- Review with team leads and managers
- Identify users who:
- Haven't logged in recently
- Have excessive permissions
- Need updated access for new roles
- Make necessary changes
- Document the review
After Organizational Changes:
- Review access after mergers, acquisitions, or restructuring
- Update project access for team reassignments
- Align permissions with new organizational structure
Security
Principle of Least Privilege:
- Grant minimum access needed for user's role
- Regularly review and downgrade unnecessary elevated access
- Use Read-Only for stakeholders who only need visibility
- Keep records of permission changes
- Document why changes were made
- Note who approved the changes
- Maintain for compliance purposes
Separation of Duties:
- Don't give everyone Admin access
- Separate billing access (Owner) from operational access
- Distribute Admin responsibilities among multiple people
Communication
Notify Users of Changes:
Hi [Name],
Your Kissmetrics access has been updated:
Previous: User
Current: Admin
This change gives you the ability to manage team members and configure
tracking settings. Please let me know if you have any questions.
Best regards,
[Your Name]
Document Reasons:
- Keep internal notes on why access was changed
- Helps during future audits and reviews
- Provides context for other administrators
Troubleshooting
Changes Not Taking Effect
Issue: User still has old permissions after update
Solutions:
- Ask user to log out and log back in
- Clear browser cache and cookies
- Wait 5-10 minutes for changes to propagate
- Verify the change was saved (check team list)
- Try updating again
Cannot Change Certain Users
Issue: Edit button is grayed out or missing
Possible Causes:
- User is the account Owner (can't be downgraded)
- You don't have permission to edit that user
- User is managed by SSO/SAML
- Account owner restrictions
Solutions:
- Contact account Owner for help
- Check your own permission level
- For SSO users, changes may need to be made in SSO provider
User Lost Access After Update
Issue: User can't access Kissmetrics after permission change
Immediate Fix:
- Go to Settings → Team
- Find the user
- Verify their permission level
- If accidentally removed, re-invite the user
- If downgraded too far, upgrade to appropriate level
Prevention:
- Double-check changes before saving
- Test with less critical users first
- Keep Owner credentials accessible
Cannot Assign Owner Permission
Issue: Can't make someone else an Owner
Reason: Most accounts limit Owner designation
Solutions:
- Current Owner must transfer ownership (if supported)
- Contact Kissmetrics support for assistance
- Use Admin permission for most management tasks
Bulk Permission Updates
Updating Multiple Users
For updating several users at once:
Create a Spreadsheet:
- List all users needing updates
- Note current and desired permissions
- Get approval from relevant stakeholders
Make Changes Systematically:
- Update users one at a time
- Check off completed changes
- Test access for critical users
Verify All Changes:
- Review team list to confirm updates
- Spot-check with affected users
- Document completion
Department-Wide Changes
When restructuring team access:
Plan the Changes:
- Map current permissions
- Define new permission structure
- Get stakeholder approval
Communicate in Advance:
- Notify affected users before changes
- Explain reasons for updates
- Provide timeline
Implement During Low-Usage Time:
- Make changes during off-hours if possible
- Reduces disruption
- Easier to troubleshoot issues
Verify and Support:
- Confirm all changes applied correctly
- Be available for user questions
- Monitor for access issues
API-Based Updates
For programmatic permission management:
# Update user permission via API
curl -X PUT https://api.kissmetrics.com/v1/users/{user_id} \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"role": "admin",
"projects": ["project-1", "project-2"]
}'
Use Cases:
- Automated provisioning systems
- Integration with HR systems
- Bulk updates via script
- Scheduled permission rotations
Compliance Tracking
Documentation Requirements
Maintain records of:
- Who made the permission change
- When it was made
- Previous permission level
- New permission level
- Reason for change
- Approval (if required)
Example Log Entry:
Date: 2024-03-15
Changed by: admin@company.com
User affected: john.doe@company.com
Change: User → Admin
Reason: Promoted to Analytics Team Lead
Approved by: manager@company.com
Audit Readiness
For SOC 2, ISO 27001, or other compliance frameworks:
- Access Review Schedule: Quarterly or as required
- Change Approval Process: Document who can approve changes
- Separation of Duties: Ensure no single person has unchecked access
- Monitoring: Regular review of permission changes
- Retention: Keep logs for required period (often 7 years)
Next Steps
After updating user access:
- Notify the User: Inform them of the change and what it means
- Update Documentation: Reflect changes in internal access matrices
- Monitor Usage: Ensure user can perform new responsibilities
- Schedule Follow-Up: Set reminder for next access review
- Document Change: Record in your access management system
Related Documentation: