Yasa Account is the shared place for your personal profile, preferences and sign-in across connected Yasa services. Use it to review the identity you are using, manage supported settings and find the company, project or hosting context available to you. Each application still controls access to its own work and resources.
That gives everyday settings a consistent home. You can review a regional preference, check a signed-in session or inspect a permitted connection without treating every service as a separate identity. Meanwhile, the actual projects, invoices and hosting operations stay in the applications designed for them.
What Yasa Account connects
Account brings together personal information, language and regional preferences, security and sign-in, companies, projects and connected-service settings. It also provides the available agent, SFTP, payment-detail and PC Shop sections for your identity. What you can see and change depends on the relevant service and your permissions.
For a wider introduction, read our Yasa Ecosystem overview. Account supplies shared identity and settings within that family. It does not turn a public registration into access to every company, project, invoice or infrastructure resource.
Sign in with the identity you already use
Start from the service you want to use and choose Sign in. On the shared account page, use an available method for your existing identity and complete its verification. Then return to the requested app and allow the workspace to finish loading.
Yasa Account currently offers Google sign-in and email with a password. If you already use a Yasa service, try that existing identity first. Otherwise, creating another account can leave you looking at a different set of records. The service sign-in guide explains the normal route.
For a genuinely new identity, use the supported account-creation flow and confirm email verification when required. Keep verification links private. The registration guide distinguishes a submitted form from a verified account and explains that service invitations and memberships remain separate.
Keep your profile and regional preferences useful
First, open Personal information to review the editable profile fields. Then save a change and reopen the section to confirm it. However, the displayed sign-in email is read-only there: changing a display name or avatar colour does not change that identity or merge accounts. The profile guide explains the scope.
Next, use regional settings for the supported language, number and date locale, time zone and other available display choices. A language and a date-format locale serve different purposes. For example, someone can prefer an English interface with a particular regional date format.
After saving, reopen the affected service and inspect its display. The regional preferences guide explains this process. A display currency preference does not rewrite an existing invoice or payment record, so keep business amounts in their proper billing context.
Manage the right company and project context
Companies and billing keeps business information separate from your personal profile. First, select the intended company or workspace. Then review the information, invoice preferences, payment details or tax settings your role permits. Save the intended change and check the accepted values afterward.
The company settings guide covers that selection. For actual invoice preparation and history, our Midas billing guide explains the business workflow. Changing a personal display preference is a different task from editing a company’s billing information.
Projects and teams provides the permitted project context and related preferences. Use Hercules for the tasks and collaboration themselves; our Hercules project guide explains that work. The team settings guide also covers available invitation and saved-view controls.
For professional opportunities, keep shared identity distinct from your skills profile. The SkillJobber guide explains professional details, company representation and identity-specific membership. A company choice should always be one you are permitted to represent.
Understand why sign-in and service access are separate
Three questions help explain access: which identity is signed in, whether the app has connected its own session, and whether that identity may use the selected workspace. A name in a shared header answers less than those three questions together. Enter the actual app and inspect its completed loading state. For hardware records and community actions, our PC Builder guide explains that app’s session and verification requirements.
If work appears missing, check the identity, selected workspace and filters first. Then ask the appropriate owner to review an invitation or role when needed. The access and sign-out guide explains why an unavailable workspace and a sign-in problem can need different remedies.
Nexus is invitation-only and requires the appropriate Google verification and resource assignments. Account’s hosting section lets you review the permitted context, while actual website or server operations belong in Nexus. Our hosting and infrastructure guide explains those resource boundaries.
Review security and sessions in Yasa Account
Use the available security controls for your existing identity. Where offered, Connect Google or password setup can add a supported sign-in method after verification. Keep access to the method you already use until the new one is confirmed. The sign-in methods guide explains this sequence.
Devices and sessions shows the Account sessions you can manage. Identify the intended browser before using a session-ending control, then verify the result in the affected app or browser. Also use app-specific sign-out where appropriate. The sessions guide distinguishes Account state from other provider sessions.
For recovery, start from the normal Account page. Use the password-recovery option for a password identity, or check the selected Google identity for provider sign-in. Follow the newest valid recovery message and keep its link private. The recovery guide explains what to report if the normal flow remains unavailable.
Keep agent and file connections tied to permitted work
Yasa Account provides Agent access for the Hercules projects, Midas workspaces and Nexus services your identity may use. An agent token lets the configured application discover those permitted resources. However, it does not create missing permissions or grant host administration.
Review the token’s name, expiry, status and available history. Store its secret only in the intended private agent configuration. The agent-token guide explains creation, replacement and revocation. Browser sign-out does not revoke that token, and replacing it requires updating the agents that used the previous secret.
SFTP connections use separate file-transfer credentials for assigned websites or game servers. Choose the exact resource and environment, inspect the connection details privately and verify the host fingerprint in the client. The SFTP guide explains its controls. Changing an agent token and changing an SFTP password affect different connections.
For example, a person preparing a permitted website change can inspect the assigned environment before choosing an agent or file-transfer client. Keep the task and target clear, then check the actual result in the site. Our MCP security guide provides further reading on permission and untrusted-content risks.
Separate payment preferences from business outcomes
The Payments section stores supported private PayPal or bank-transfer details for making or receiving payments. Review the intended identity and the purpose of the method, then save the accepted list. The payment settings guide explains the fields and the confirmation.
Saving those details does not authenticate a provider, send money or establish that an invoice was paid. Instead, each service retains its own billing history and supported checkout process. Meanwhile, our Yasa Pay guide explains supported checkout and billing handoffs. Therefore, check the relevant invoice, shop order or subscription when you need to understand an actual financial outcome.
Review shop records, email choices and privacy requests
For a connected PC Shop identity, Account provides Orders, Support and Delivery views. Check the intended order or conversation and the delivery fields available to your account. A saved address change does not itself amend an existing order. The PC Shop account guide explains that workflow. Our Yasa PC buying guide follows the product-to-order journey.
Email preferences groups supported service choices and notification categories. In particular, read the purpose of each option before saving; product news has its own marketing choice. The email preferences guide also explains inherited choices, daily summaries and existing unsubscribe settings. Mailbox alerts and hosted email have their own controls; our hosted Webmail guide explains those settings.
Privacy and data provides the supported request process for your own information. Choose the intended request and services, retain its reference and inspect the current status. The privacy request guide distinguishes a request recorded for review from a completed export, correction or removal.
Start with the Yasa Account setting you need
Begin with the identity and service involved, then open the section that owns the setting. Review the intended context, save once and reopen the result. This simple sequence helps keep personal preferences, company information and application work understandable as you move between services.
Use the public Account help guides for current steps. If something remains unclear, contact Yasa with the service, approximate time and displayed error. Keep passwords, verification links, payment credentials and agent secrets out of the message.
