Choose a credential
Your browser session is used for the website. Personal access tokens authenticate terminal Git and other supported token endpoints. Ramuvo Workspace uses a browser-authorized OAuth access token. These credentials are separate; one login does not configure every client.
Create and manage personal access tokens
- Open Settings → Personal access tokens.
- Name the token for its purpose and set an expiry.
- Limit repository, capability, branch, and path access using the controls offered by the form.
- Generate and copy the token immediately. Revoke it when it is no longer needed.
Before you continue: A token is shown once. If lost, create a replacement and revoke the old token. Never put a token into a Git URL or commit it.
Authorize connected applications
Connected applications ask you to approve access in the browser. Read the application name and permission list before consenting. The application’s token is bound to those permissions and your existing account access.
Workspace OAuth scopes
openid and profile identify your account and public profile. repo:read permits accessible repository listing and Git/LFS reads. repo:create permits repository creation where your role allows it. repo:write permits Git pushes and LFS uploads. org:read permits listing organization memberships.
The extension requests additional scopes when a workflow needs them. Existing grants are not silently upgraded. Its access tokens expire after one hour and there are no refresh tokens. Reconnect to authorize another session.
Remove access
Revoke a token in token settings. Disconnect an OAuth application in OAuth settings to revoke its grants. In the editor, Sign Out clears the stored session and attempts token revocation. If the network is unavailable, finish remote revocation in browser settings.
Revocation and scope checks do not replace role checks. A restricted token cannot gain access by supplying a browser cookie alongside it.