Use this guide when you want to control who can access your Pressidium account, your websites, and the technical tools used to manage them.

From here, you can decide whether you need to manage Dashboard users, SFTP users, SSH access, database access, or review team activity.

What this guide covers

This guide helps you find the right access-management task.

Use it to:

  • Invite and manage Dashboard users
  • Understand Dashboard roles and permissions
  • Manage SFTP access
  • Set up and manage SSH access
  • Create and manage SSH keys
  • Give database access to a third party
  • Review your team’s activity
  • Understand the ninukisadm system user

When to use

Use this guide when:

  • You need to give a team member access to your Pressidium account
  • You want to limit what a user can see or do
  • A developer needs SFTP, SSH, or database access
  • You want to audit recent team activity
  • You see a system user you do not recognize
  • You are preparing access for an agency, freelancer, or technical partner

Manage Dashboard users

Dashboard users are people who can log in to the Pressidium Dashboard and manage account or website resources, depending on their role.

To add, remove, or update Dashboard users, follow:

Manage role-based Dashboard users

To understand what each role can do before assigning access, review:

Roles and permissions of Dashboard users

Use role-based access when you want users to have only the permissions they need.

Manage SFTP access

SFTP access lets users connect to your site files securely.

Use SFTP when a developer, agency, or technical team member needs file-level access without giving them full Dashboard access.

To create, update, or remove SFTP users, follow:

Manage SFTP users

Manage SSH access

SSH access is used for command-line access to a website environment.

Start here if you want to understand whether SSH access is available:

Do you provide SSH access?

To manage SSH access for your WordPress site, follow:

Managing SSH access

To create or manage the keys used for SSH authentication, follow:

Create and manage SSH keys

Important: SSH access should only be granted to trusted technical users who understand the impact of command-line changes.

Give database access to a third party

Database access may be needed when a developer, agency, or external technical partner needs to inspect or work with your site database.

To give database access safely, follow:

How do I give database access to a third party?

Only share database access with trusted users. Database changes can affect site content, settings, users, orders, and application behavior.

Review team activity

Use the activity log when you need to check what actions were taken by users in your account.

This is useful when you want to:

  • Audit recent account activity
  • Confirm who made a change
  • Review access-related actions
  • Investigate an unexpected configuration change

To review recent activity, follow:

Review your team’s activity with the activity log

Understand the ninukisadm user

You may see the ninukisadm user in your WordPress site.

This is a Pressidium system user used for platform operations and support-related tasks.

To understand what it is and why it exists, review:

Who is ninukisadm?

Common access tasks

I want to invite someone to the Pressidium Dashboard

Use: Manage role-based Dashboard users

Then review: Roles and permissions of Dashboard users

I want a developer to access site files

Use: Manage SFTP users

I want a developer to use command-line access

Start with: Do you provide SSH access?

Then follow: Managing SSH access

I want to add or update SSH keys

Use: Create and manage SSH keys

I want to give a third party database access

Use: How do I give database access to a third party?

I want to check what a team member changed

Use: Review your team’s activity with the activity log

Best practices

Give each user the lowest level of access they need to complete their work.

Remove access when a user, contractor, or agency no longer needs it.

Use separate users for separate people. Avoid sharing credentials between team members.

Review team activity when investigating account or website changes.

Be careful with SSH and database access. These access types are intended for trusted technical users.

Need help?

Contact Support if you are unsure which type of access to grant or if you need help reviewing access for a specific user.

Include:

  • Account name
  • Website name, if relevant
  • User email address, if relevant
  • Type of access needed
  • What the user needs to do

Where to go next