Team Overview
The team section is where you manage shared account access for other people who need to work inside your PerLod Dash environment.
It helps you organize access in a more structured way instead of relying on a single account for all actions.
What the team section is for
Use the team section when you want to:
- review team members
- invite another user into the account workspace
- check who currently has access
- review permission assignments
- see whether an invitation is still pending
- update or remove access when needed
This section is useful when more than one person needs to work inside the same account environment.
What you may see in team
Depending on the current setup, the team area may include sections such as:
- member list
- pending invitations
- permission labels
- current access state
- invitation form
- edit and remove actions
The exact layout may change over time, but the purpose remains the same.
Why team access matters
Using team access helps with:
- separating work between different users
- reducing dependency on one main login
- keeping account activity more organized
- supporting shared operational workflows across services, billing, and support
This is especially useful for business accounts or shared operational teams.
Start from team overview
A good team workflow usually starts from the main team page.
Use it as the first place to check:
- who already has access
- which members are active
- whether any invitation is still pending
- whether permissions still match current responsibilities
- whether a member or invitation needs action
Before making any change, review the visible team information carefully.
Common team workflows
Typical examples include:
- inviting a new team member
- reviewing an invitation that is still pending
- updating permissions for an existing member
- removing access when a person no longer needs it
Always review access changes carefully before confirming them.
Team and the rest of Dash
The team section is for shared account access management.
Other detailed work usually happens elsewhere in Dash.
For example:
- use Services for VPS, Dedicated Server, GPU, or domain management
- use Billing for invoices, payments, and wallet-related actions
- use Support for ticket workflows
- use Profile for account identity and profile settings
This keeps shared access management separate from service-specific work.
If something looks incorrect
If a member is missing, an invitation does not appear correctly, or access information looks wrong:
- refresh the page
- review the team list again
- confirm that you are in the correct account
- contact support if the issue continues
When contacting support, include a short description of the issue and the related member or invitation state.