Account and access

Account and team

Your account details, password, open sessions and sign-in records; roles in the tenant, the tenant's members, teams and team managers, and showing a project only to the members you choose.

Open as plain text

Everything about your account is on the Ayarlar (Settings) page; you open it from the user menu at the top right. The tenant's members and teams are on the Ekip (Team) page in the left menu, and who can see a project is set in the project's own settings.

#Your account details

The Hesap (Account) section of the Settings page shows your username, your name, your e-mail address and which tenant you are in with which role. You change your first and last name yourself with «Adımı düzenle» (Edit my name). Your administrator changes your e-mail address; the username does not change. Adding you to a tenant and your role there are up to that tenant's admin or the platform admin.

In the Görünüm (Appearance) section you choose the theme: «Açık» (Light), «Karanlık» (Dark) or «Otomatik» (Automatic), which follows your device. Times are shown in your time zone.

#Password

The «Parolamı değiştir» (Change my password) button first asks you to verify your identity: you sign in again with your current password, then set the new password. The «Öteki oturumlarımı kapat» (Close my other sessions) box comes ticked: this session stays open, and other browsers, the phone app and assistant connections have to sign in again. If you clear the box, sessions stay open and you close them from the list below.

#Sign-in methods

In Ayarlar › Güvenlik › Giriş yöntemleri (Settings › Security › Sign-in methods) you add other methods alongside your password:

Passkey (geçiş anahtarı): you sign in without typing a password, with your fingerprint, face or device PIN. It is created on your computer or phone. The sign-in page shows a passkey button; your browser may also offer it in the user name box.
Authenticator app (doğrulama uygulaması): after your password you enter the code from the app on your phone. No code is asked when you sign in with a passkey.

If passkeys are enabled in your installation and you have not added one on this device, the panel asks after you sign in whether you want to add one. If you already have one here, choose Bu cihazda var (It is on this device) and it will not ask again in this browser. If you choose Şimdi değil (Not now), it does not ask again in this browser for a while; you can add one from this section at any time.

You can rename and delete each method. Deleting first asks you to verify your identity.

If you tick Beni hatırla (Remember me) on the sign-in page, your session stays open in this browser for days. Do not tick it on a shared computer.

If you lose your phone or key, sign in with your password. If you cannot because a code is required, ask your platform administrator: after verifying your identity they reset your methods and you add them again.

#Recent sign-ins and sessions

Son girişler (Recent sign-ins): your sign-ins, failed sign-in attempts and sign-outs, each with its time and address. If you see an address or a time you do not recognise, change your password and let your platform admin know.
Son oturumlar (Recent sessions): your sessions opened in the panel, in assistants and in the mobile app; a badge tells the open ones from the closed ones. Close a session you do not recognise with «Kapat» (Close); that device or assistant then has to sign in again. After you close an assistant's session you can connect the same assistant again right away. If an assistant row cannot be closed on its own, the row says which row to close it from.
Tüm oturumlardan çık (Sign out of all sessions): you are signed out of every browser including this one, every phone and every assistant; you are first asked to sign in again.

#Assistant access keys

If your assistant cannot sign in through a browser, you can create a key in the MCP erişim anahtarları (MCP access keys) section of Ayarlar (Settings). The key works only for the assistant connection; administrator tools are not available with a key.

Create the key
Press the «Anahtar oluştur» (Create key) button. You are first asked to verify your identity again. Give the key a name you will recognise (do not include personal information) and choose how long it is valid: 7, 30, 60 and 90 days; the default is 30 days.
Copy it right away
The key is shown only once. Once the dialog closes you cannot see it again; if you lose it, revoke it and create a new one.
Add it to your assistant
Add the key to your assistant's MCP settings as an Authorization: Bearer … header. Don't write the key into a shared file or a file that goes into a repository; keep it in an environment variable on your computer (for example TURGUZ_MCP_ANAHTARI).

You can have at most 5 active keys at a time. Revoke keys you no longer use with «İptal et» (Revoke); the connection of the assistant using that key is cut off within a minute. You get a notification when you create a key and when a key is revoked.

#Tenant and roles

What each role can do is on the Getting started page. You see your role in Settings, next to the tenant's name.

#The tenant's members

The Üyeler (Members) tab of the Ekip (Team) page lists all of the tenant's members and their roles, and the Ekipler (Teams) tab lists the teams inside the tenant. In a long list, use the search box and the Ekip (Team) and Rol (Role) filters; the list opens with 25 people, and the button below the list brings the rest. The «Kiracı yöneticisi» (Tenant admin) adds members to the tenant, changes their roles and removes them from the tenant.

#Adding a member to the tenant

Open the dialog
On the Üyeler (Members) tab, press the «+ Üye ekle» (+ Add member) button.
Enter the person
In the «Kullanıcı adı ya da e-posta» (Username or e-mail) field, type the person's username or e-mail address in full; upper and lower case do not matter. People in your organisation are not listed, so you need to know the name exactly.
Choose the role and add
Choose the role from the «Rol» (Role) list and press the «Kiracıya ekle» (Add to tenant) button.

If the name or address you type does not match an account that can be added to the tenant, you only get a "not found" answer; the reason is not given. Check the spelling; if the person has no account, ask your platform admin to create one.
After many unmatched attempts in a short time, adding pauses temporarily; try again a little later.
You can also do the same with your AI assistant; there too you type the person's username or e-mail in full.

#Changing a role and removing from the tenant

You change a member's role from the «⋯» menu at the end of their row. You can also select several people and change their role together with «Rolünü değiştir» (Change role); they are updated one by one, and any that can't be changed are skipped and listed with the reason.
With «Bilgileri düzenle» (Edit details) you correct a member's first name, last name and e-mail address; the person gets a notification saying which details changed. A tenant admin cannot edit themselves or other tenant admins this way. To change an e-mail address, you must have signed in again recently.
«Kiracıdan çıkar» (Remove from tenant) removes the member from the tenant. The removed person's permissions in this tenant, server access, project memberships and team membership are removed as well. Their server leases in this tenant are left without an owner; tenant admins get a notification, and if no decision is made in time the servers are stopped.
A person who is added, whose role changes or who is removed learns about it through a notification; tenant admins also see the change through a notification.
The tenant's last tenant admin cannot give up the role or be removed from the tenant; first make someone else a tenant admin.

A member managing someone else's server is a separate permission: Team members and server access.

#Teams and team managers

The tenant admin can divide the tenant's members into teams. A person is in at most one team in a tenant. A team can have one or more team managers; a team manager is a Developer in the tenant, and their authority applies only to their own team.

On the Ekipler (Teams) tab, «+ Ekip oluştur» (+ Create team) creates a team. Each team is one row; clicking the row opens its first members and the team's resources. In the row's «⋯» menu, «Adlandır» (Rename) changes its name and «Ekibi sil» (Delete team) deletes it; the members of a deleted team are left without a team, and their roles, servers and projects do not change.
«+ Ekibe al» (+ Add to team) adds a person to the team: you either pick a member of the tenant or type the exact user name or email of someone who is not in the tenant; that person is added to the tenant as well, and tenant admins see it through a notification.
The tenant admin makes a member of the team its manager with «Ekip yöneticisi yap» (Make team manager) and takes it back with «Yöneticiliği kaldır» (Remove manager role). A viewer cannot be a team manager.
A team manager sees only their own team; the Team page has a tab named after their team. They add people to it; when adding someone who is not in the tenant they can give only the Developer or Viewer role. They remove members of their team with «Ekipten çıkar» (Remove from team) and switch their role between Developer and Viewer. They cannot touch themselves, the team's other managers or tenant admins; only a tenant admin moves a person in another team between teams.
«Ekipten çıkar» (Remove from team) does not remove the person from the tenant; their role in the tenant does not change.
The tenant admin changes a person's team in one step with «Ekibini değiştir» (Change team) in the row's «⋯» menu on the Üyeler (Members) tab; «Ekipsiz» (No team) removes the person from their team. They can also select several people and move them together with «Ekibe taşı» (Move to team). Changing a team manager's team asks for confirmation: they become a member in the new team.
A team manager sees the servers and projects of their team's members in the Ekibin kaynakları (Team's resources) section; the list is read-only, and a server or project is managed by its owner and those with permission. A team manager also sees a hidden project only if they are a member of that project.
If team and personal quotas are on in the tenant, a team manager gives their team's members personal quotas within the team's share: Team and personal quotas.
If a team manager's role drops to Viewer or the person leaves the tenant, the team manager role goes with it. If a team has no manager left, tenant admins get a notification; the tenant admin then manages the team.

#Team settings

Only the tenant admin sees the Ayarlar (Settings) tab of the Team page:

Kiracı (Tenant): the tenant's name shown in the panel. «Adı değiştir» (Rename) changes only the displayed name; servers, projects and memberships stay as they are.
Yapay zekâ asistanı bağlantısı (AI assistant connection): members can connect Turguz to an AI assistant with their own consent (AI assistant). While «Bu kiracıda yasakla» (Ban in this tenant) is on, members' assistants can't see this tenant's resources; every member of the tenant gets a notification. A person's own consent stays on the Ayarlar (Settings) page.
Ziyaretçi sayımı (Visitor counting): the «Sitelerine gelen trafik» (Traffic to your sites) card on the welcome page also shows unique visitors and page views of your sites. Visitors are counted without cookies and without identifying anyone; nothing is added to your site and known bots are not counted. While «Sitelerimde ziyaretçileri say» (Count visitors on my sites) is off, your sites are not counted. If counting has not been turned on for the platform, the card shows only the request count.
Ekip yalıtımı (Team isolation): whether teams can see each other's resources. Before you turn it on, it shows which resource goes to which team, who will no longer see what, and which API connections are affected.

#Showing a project only to the members you choose

On the Projeler (Projects) page, the project's Görünürlük ve üyeler (Visibility and members) section gives two possible answers to the question «Kimler görür?» (Who can see it?):

«Kiracıdaki herkes» (Everyone in the tenant): all members of the tenant see the project and do whatever their role allows.
«Yalnız seçtiğim üyeler» (Only members I choose): only the members you add and the tenant admins see the project. At first, only you are on the list.

Each person on the list is either «Yönetici» (Admin) or «Üye» (Member) in the project. At least one project admin must remain in the project; a person with the «İzleyici» (Viewer) role cannot be made a project admin. Project admins and tenant admins change this setting. When you remove someone from the list, renew the secret values, since that person may have seen them before.

#If the tenant is suspended

The platform admin can suspend a tenant. A suspended tenant's sites go offline and its servers stop; its data is not deleted. Visitors to the sites see the "This site is temporarily unavailable" page; they are not told the reason. Members receive the Kiracınız askıya alındı (Your tenant was suspended) notification with the reason, and cannot take any action in the panel until the tenant is reopened. When the tenant is reopened, the Kiracınız yeniden açıldı (Your tenant was reopened) notification arrives; your lease and retention periods are extended by the time spent suspended.