Account and security

Profile

Your profile settings let you update account information, your profile photo, and social links.

When you register with Google or GitHub, Inalia copies your provider's profile photo if it is available as a JPG or PNG of up to 1 MB. If it cannot be imported, your initials are shown instead. Later sign-ins and linking a provider do not replace your photo or restore one you removed.

To change your photo, open Profile Information, select a JPG or PNG file (maximum 1 MB), and select Save changes. You can select a replacement while your current photo is still displayed. Remove profile photo deletes the saved image and restores the initials placeholder; it does not change your Google or GitHub photo.

Speaker information and social links can appear in the public participation experience. Only add information you intend to share with your audience.

Logging in

You can log in with your email and password, Google, or GitHub. When you select Google or GitHub on the login page, Inalia remembers that choice in your browser and shows a Last used badge next time. The badge reflects your last selection, not whether the login succeeded. It is not shown for email and password, and does not follow you across browsers or devices. If browser storage is unavailable or cleared, the badge will not appear.

Signing in with GitHub

If your GitHub account is not connected to an Inalia account, signing in with GitHub creates an account using your GitHub profile and email address. If that email address is already registered, log in to the existing Inalia account first, then connect GitHub from your profile's security settings.

Access and email verification

Follow any verification or access instructions shown after registration. An account that is signed in may still need to complete these steps before accessing talks or integrations.

Password and two-factor authentication

Use the security settings to update your password and configure two-factor authentication.

Complete the confirmation step before relying on two-factor authentication. Store recovery codes securely so you can recover access if you lose your authenticator.

Browser sessions

Review browser sessions in security settings and sign out other sessions when needed, especially after using shared devices.

Connected apps

When an OAuth app asks to connect, Inalia shows an authorization screen with the app's name, your signed-in email, and any requested permissions. Choose Authorize only if you trust the app, or Deny to decline access. After either choice, you return to the app. If the authorization request is unavailable or has expired, start the connection again from the app you want to connect.

MCP apps use the same authorization screen. Read access (mcp:read) lets an app read your talks, questions, results, and presentation components. Write access (mcp:write) also lets it create, change, and delete talks and questions, clear answers, and control live presentations. Read access is mandatory and cannot be unchecked. If the app requests Write access, it is selected by default, but you can uncheck it before choosing Authorize to grant read-only access. You can only grant permissions the app requested. Choose Deny to grant no access. Some app features may not work without their required permissions. Review the requested permissions carefully before authorizing write access.

Open Security in your profile settings and review Connected Apps to see OAuth apps with active access to your account. An app remains listed if it can renew its access, even when its current access token has expired.

Choose Disconnect, then confirm to revoke all of that app's access and refresh tokens for your account. Pending authorizations for the app are also revoked. Other apps, other users, browser sessions, and personal API tokens are not affected. Disconnecting does not delete data the app has already received. To use the app again, authorize it again.

OAuth apps are separate from Google and GitHub sign-in connections.

API tokens

Tokens grant integration access with their configured permissions. Create a separate named token for each integration, grant only the permissions it needs, and delete unused tokens.

Tokens are for integrations, not account administration. See Slidev and demo mode.

Delete your account

Account deletion is destructive. Review the confirmation carefully and retain anything you need before proceeding.

For data-handling details and privacy requests, consult the Privacy Policy.