Your Team Can Manage Hippius Cloud Resources Without Sharing a Single Password

Hippius (SN75) has introduced Shared Accounts, allowing multiple people to manage cloud infrastructure through one account without sharing login credentials.

Each team member uses their own login, while the account owner controls access and pays for the resources used.

Hippius (SN75) is a Bittensor-powered decentralized cloud platform offering computing and storage services, including virtual machines, databases, Kubernetes, and S3 storage. The new feature makes it easier for development teams and businesses to manage these resources together.

How Shared Accounts Work

Account owners can invite team members by email and decide which services each person can access. Members retain their personal Hippius accounts and can switch between personal and shared accounts from the profile menu.

There are three permission levels:

1. Viewers see resources and settings but cannot make changes.

2. Operators perform routine tasks such as restarting virtual machines, managing backups, and uploading files to S3.

3. Admins create, modify, and delete resources within the services they are permitted to manage.

For example, a startup could give one developer access to its virtual machines while another manages databases, without either needing the owner’s credentials.

Getting Started

Getting started with Shared Accounts is straightforward through the Hippius Console. Account owners only need to follow two steps:

1. Navigate to Team → Members and invite collaborators using their email addresses.

2. Click on ‘Invite Members’ to assign the appropriate access permissions to each member and send the invitations.

Invitations expire after seven days, and accounts support up to 50 members and pending invitations by default.

Who Pays and Who Controls the Resources?

All infrastructure created by team members belongs to the account owner, and usage costs are deducted from the owner’s balance. Members cannot add funds or perform certain sensitive operations, including creating Kubernetes clusters.

Hippius also provides an audit trail that records member activities, including resource changes and access events, making it easier for owners to track what their teams are doing.

Owners can change permissions or remove members at any time without deleting the resources those members created. Shared Accounts currently cover compute services and S3 storage. Collaboration on files uses Hippius’s separate Shared Drives feature.

➛ View Hippius (SN75)’ Shared Accounts Docs Here.