Please note this is the Tennant Admin Guide - for ‘normal’ users there is additional documenten which can be found here: xxx
1.0 Introduction for administrators
As an organization administrator (tenant admin), you manage how mytranscript works for everyone in your organization. This chapter explains the admin role, what you can manage compared with a regular user, and how to reach the administrator settings.
The administrator role
A tenant admin is a regular mytranscript user with extra permissions to manage the organization. The role is granted by another administrator from the user management screen (see "User management"). Most people in your organization are regular users; only a small number need to be administrators. The role is directly based upon the “Application Admin” role in MyOTYS.
What admins can manage
In addition to everything a regular user can do, an administrator can:
Manage users: view them, control access, and grant or remove the admin role.
Configure organization-wide recording rules that apply to everyone.
Configure the recording bot's name and behavior.
Manage organization settings, including allowed email domains and the default language.
Customize the AI instructions used to generate meeting summaries.
View the organization's plan, usage, and billing.
Oversee the OTYS connection.
Review audit logs, OTYS sync logs, and AI usage logs.
What admins do not manage
Some things are intentionally outside the tenant admin role:
Individual users' private content is theirs; admins manage access and settings, not the personal contents of every meeting.
Platform-level operations and system administration are handled by the service operator, not by tenant admins, and are out of scope for this guide.
Reaching the administrator settings
Sign in to mytranscript.
Choose Organization in the navigation.
The "Organization Settings" page is organized into tabs, each covered by a chapter in this guide:
Users
Recording Rules
Bot Settings
Internal Domains
AI Prompts
Billing
Audit Logs
Sync Logs (the OTYS sync log)
AI Usage Logs
If you do not see the Organization option, your account does not have the tenant admin role.
2.0 User management
The Users tab under "Organization Settings" is where you manage the people in your organization. This chapter covers viewing users, how users gain access through OTYS, roles and permissions, the user detail view, and blocking or removing access.
Viewing users
Choose Organization, then the Users tab. You see a list of everyone in your organization with columns such as:
Name and Email
Plan (their recording plan, or "No plan")
Admin (whether they are a tenant admin)
Calendar Connected
Meetings (total number)
Status (Active or Blocked)
You can filter the list by Active and Blocked users and page through large lists.
How users gain access (OTYS SSO)
You do not normally create users by hand. Instead, access is governed by OTYS Single Sign-On:
When someone from your organization signs in to mytranscript through OTYS for the first time, mytranscript automatically creates their account using their OTYS profile (name and email).
New users joining this way are automatically assigned your organization's default plan, if you have set one (see "Plans, billing, and quota").
New users are regular users by default, not administrators.
This means the practical way to "invite" someone is to ensure they have an OTYS account with a valid email and have them open mytranscript from OTYS. To remove access, you block or deactivate the user in mytranscript (see below); you also manage their underlying access in OTYS.
Roles and permissions
mytranscript has two roles within an organization:
Regular user. Can record, review, and share their own meetings, and manage their personal settings and rules.
Tenant admin. Everything a regular user can do, plus management of the organization (users, rules, bot, domains, AI prompts, billing, OTYS connection, and logs).
To change someone's role, open their user detail view and use Make tenant admin or Remove tenant admin. You cannot remove the admin role from your own account, which prevents an organization from being left without an administrator.
The user detail view
Select a user to open their detail view, which has an overview and management options.
The overview shows:
User information (email, last sign-in, total meetings, created date).
Their current plan and monthly usage (used and limit).
Their calendar connection status.
Their personal recording rules.
From the management options you can:
Change or remove the user's plan, including scheduling a change for next month.
Toggle the tenant admin role.
Block or unblock the user.
Blocking and unblocking a user
Blocking is how you stop someone from using mytranscript while keeping their data.
Choose Block User. A blocked user cannot sign in or use the application. Their plan is retained, but billing for them stops while they are blocked.
To restore access, choose Unblock User. They can sign in again and billing resumes.
mytranscript warns you before blocking, especially if the user has active recordings, since blocking may interrupt them.
Removing access
Because access is tied to OTYS SSO, the way to remove someone from mytranscript is to block them (so they can no longer sign in) and to manage their access in OTYS. Blocking preserves their meetings and history for your records and for compliance. See "Data, privacy, and retention" for how data is handled.
Setting the default plan for new users
From the Users tab you can configure the Default Plan that is automatically assigned to new users who join through OTYS SSO. See "Plans, billing, and quota" for details.
3.0 Organization-wide recording rules
Recording rules decide which meetings mytranscript records automatically. Organization-wide rules apply across your whole organization and set the baseline for everyone. This chapter explains how to configure them and how they interact with users' personal rules.
Where to find them
Choose Organization, then the Recording Rules tab.
How rules work
Each rule is either:
Record — if a calendar event matches the rule's conditions, record it.
Skip — if a calendar event matches the conditions, do not record it.
Rules apply to meetings that come from users' connected calendars and that have a video link. A rule's conditions can match on the meeting title, an attendee's email, the number of attendees, or the meeting duration. When a rule has several conditions, all of them must be met for the rule to apply.
Quick setup
If you are starting from scratch, use the quick setup:
Apply Default Rules sets up a recommended configuration. If you have configured internal domains, this skips internal team meetings and records external meetings. Without internal domains, it records all meetings that have a video link.
You can refine the result afterwards.
Adding rules
You can build your rule set from presets or from scratch:
Add Preset lets you pick from ready-made rules, such as:
Skip internal meetings (do not record meetings where all attendees are from your organization).
Record all meetings (with a video link).
Skip short meetings (under 15 minutes).
Record interviews only (title contains "interview").
Skip one-on-one meetings (only two attendees).
Add Custom lets you create a rule with your own name, type, and conditions.
Required versus optional rules
For each organization rule you can decide how much control users have:
Required. The rule always applies and individual users cannot disable it for their own calendars.
Optional. Users may disable the rule for their own calendar if they choose.
Use Make required or Make optional on a rule to switch between the two. Use required rules for policies that must hold for everyone (for example, a compliance rule), and optional rules for sensible defaults users can opt out of.
How organization rules interact with personal rules
When mytranscript decides whether to record one of a user's calendar meetings, it evaluates the rules in this order:
Organization rules (set here) are applied first.
The user's personal rules are applied next and can refine the outcome, except where an organization rule is Required.
A manual choice on a specific event (the user enabling or disabling recording on the "Calendar" screen) always wins for that event.
This lets you set a safe organization-wide baseline while still allowing users to tailor recording to their own work, within the limits you set.
Editing, disabling, and removing rules
Each rule offers options to Edit rule, Disable rule (keep it but pause it), and Delete rule. You can also restore the standard rule set or reset to the recommended defaults; mytranscript confirms before replacing your existing rules.
4.0 Bot configuration
The recording bot is the participant that joins your organization's online meetings to record them. The Bot Settings tab lets you control how it presents itself and when it joins. This chapter explains each setting.
Where to find bot settings
Choose Organization, then the Bot Settings tab.
Bot name
The Bot name is the display name shown to everyone in a meeting when the bot joins (in the participant list). Choose a name that clearly identifies it as a note-taker, for example "AI Note Taker". If you leave it empty, a default name is used.
A clear name reinforces that the meeting is being recorded and helps participants understand who the extra participant is.
Join timing
Join timing controls how early the bot joins before a scheduled meeting starts. The options are:
Just on time
1 minute before
2 minutes before
5 minutes before
Joining a little early helps ensure the bot is admitted and recording from the very start of the conversation.
Join chat message
You can have the bot post a short message in the meeting chat when it joins:
Turn on Send a chat message when the bot joins.
Enter the Chat message you want posted, for example: "Hi! I'm a note-taking assistant. I'll be recording and transcribing this meeting."
This message informs everyone in the meeting that notes are being taken, which supports a transparent, consent-friendly approach to recording.
Why these settings matter
The bot is always visible to participants, but a recognizable name and a clear chat message make recordings transparent and professional. Consider your organization's policies and local expectations around recording when choosing the name and message.
Saving changes
Make your changes and save. Bot settings apply to future meetings recorded for your organization.
5.0 Organization settings and domains
This chapter covers your organization's general settings, with a focus on internal email domains, which influence both recording rules and how participants are classified.
Internal email domains
The Internal Domains tab (shown as "Internal Email Domains") is where you tell mytranscript which email domains belong to your organization.
Choose Organization, then the Internal Domains tab.
How internal domains are used
Internal domains do two important things:
They classify attendees. Recording rules use them to tell internal people apart from external ones. For example, the "Skip internal meetings" rule relies on internal domains to recognize when every attendee is from your organization.
They mark colleagues in transcripts. A participant whose email matches an internal domain is automatically treated as a colleague in meetings. This is important because colleagues are not synced to OTYS as candidates or contacts.
In other words, getting internal domains right makes both your recording rules and your OTYS sync behave correctly.
Adding and removing domains
Enter a domain (for example, company.com) and choose Add.
To remove a domain, choose Remove domain next to it.
mytranscript validates the format and prevents duplicates. Add every domain your organization uses for email, including any secondary or regional domains.
Default language
Your organization can have a default interface language, which sets the starting language for the experience. Individual users can still choose their own language in their personal settings (see "Personal settings" in the Regular User Guide).
Organization profile
Your organization's profile (such as its name) is established when the organization is first set up, based on the OTYS connection. General organization options are managed from the "Organization Settings" tabs described throughout this guide.
Saving changes
After changing any organization setting, save. mytranscript confirms when settings are saved successfully. Changes to internal domains take effect for future meetings and rule evaluations.
6.0 AI prompt customization
You can guide how mytranscript writes summaries, action items, categories, and tags for your organization by adding your own instructions. The AI Prompts tab is where you do this. This chapter explains what these instructions do and how to use them well.
Where to find it
Choose Organization, then the AI Prompts tab.
What the instructions do
The instructions you set here are the default guidance the AI follows whenever it creates meeting summaries, action items, categories, and tags for your organization. For example, you can tell the AI to:
Use specific terminology and correct common transcription mistakes.
Emphasize particular details for recruitment or vacancy meetings.
Focus on certain points for customer calls.
Write in a particular style or tone.
Important: these instructions only affect how the AI writes its summary and related outputs. The original transcript text is never changed by them.
Adding instructions
Enter your guidance in the Default instructions field. You can write plain sentences and simple term mappings, for example:
"product x > Product X"
"Focus the summary on decisions, risks, and concrete next steps."
Save.
Smart prompt additions
To help you get started, mytranscript offers ready-made suggestions you can add with one click and then adjust. Examples include:
Terminology glossary — correct common transcription mistakes and enforce exact terms.
Recruitment interview — emphasize candidate background, motivation, experience, salary expectations, availability, fit, and next steps.
Vacancy intake — capture role context, must-have and nice-to-have skills, rate, location expectations, timeline, stakeholders, and open questions.
Customer call — focus on customer goals, pain points, objections, budget signals, decision criteria, and follow-ups.
Executive summary — start with the most important outcome, then decisions, risks, and next steps.
Risks and open questions — always surface risks and open questions when discussed.
Action ownership — include owner and due date only when explicitly spoken.
Dutch business tone — write clear, practical professional Dutch when the meeting is in Dutch.
You can add a suggestion, then edit the text to fit your organization.
Good practices
Be specific about terminology, names, and acronyms your organization uses; this noticeably improves summary quality.
Tell the AI what to focus on, but avoid asking it to invent details. The best instructions ("do not invent owners or deadlines that were not spoken") keep summaries trustworthy.
Start from a suggestion and refine it over time as you see the results.
Where to see the effect
These instructions apply to summaries generated after you save them. You can review how AI is being used across your organization, including the custom instructions applied to each request, in the AI usage logs (see "Logs and oversight").
7.0 Plans, billing, and quota
Recording capacity in mytranscript is governed by plans. Each user can be assigned a plan that grants a monthly allowance of recording minutes. This chapter explains plans, the default plan for new users, usage and quota, and the billing information available to you.
How plans work
A plan defines how many recording minutes a user gets per month and the monthly cost. Typical plans range from a free starter plan with a modest monthly allowance to higher tiers with more minutes, up to an unlimited option. The exact plans and prices available to your organization are configured for you by the service provider.
A user must have a plan to record meetings. A user with no plan sees a message that they have no active plan and cannot record until one is assigned.
Assigning and changing a user's plan
From the Users tab, open a user's detail view to manage their plan:
Assign or Change their plan.
Choose when the change takes effect: This month (the full price applies for the current month) or Next month.
Remove a plan if the user should no longer be able to record.
mytranscript helps you decide by showing the price impact and warning you if a user's recent usage suggests they would exceed a smaller plan's limit. You can also schedule a change for a future month and cancel a pending change before it applies.
The default plan for new users
So that people can start recording as soon as they join, you can set a default plan that is automatically assigned to new users who arrive through OTYS SSO.
Go to the Users tab.
Open Default Plan.
Select the plan to assign automatically (or choose none, so new users start without a plan).
Usage and quota
Each user has a monthly recording allowance based on their plan. When a user approaches or reaches their limit:
The user is notified by email, and so are the organization's administrators (see "Notifications" in the Regular User Guide).
New recordings for that user are paused until the next month or until you raise their plan.
You can see each user's used and remaining minutes in their detail view and in the user list.
Billing
Choose Organization, then the Billing tab to see the billing picture for your organization:
The number of users with a plan.
The total monthly cost.
A per-user breakdown of plan, minutes used, limit, and cost.
You can export the billing breakdown to CSV for your records.
Note that blocked users keep their plan but are not billed while blocked (see "User management").
8.0 OTYS integration setup
The OTYS integration is what connects mytranscript to your recruitment system. It governs how users sign in and how meeting notes flow back to candidates and contacts. This chapter explains how to complete the setup, what data syncs, and the controls available to you.
What the integration does
The OTYS integration provides two things:
Single Sign-On (SSO). Your users sign in to mytranscript using their OTYS accounts, with no separate password.
Transcript and summary sync. When a meeting with a candidate or contact is completed, mytranscript writes a note to the matching record in OTYS, containing the summary, the action items, and a link back to the meeting.
How sign-in works (SSO)
When a user opens mytranscript from OTYS:
mytranscript verifies the OTYS session and creates the user's account on first use, based on their OTYS profile (name and email).
The user must have a valid email address in OTYS; sign-in cannot complete without one.
The user is placed in your organization automatically and assigned your default plan if you have set one.
You do not create users manually; OTYS SSO governs who can access mytranscript. See "User management".
What data syncs to OTYS
When a meeting with a candidate or contact reaches the Completed stage, mytranscript writes a note to the matching OTYS record. The note contains:
The meeting summary (as text).
The action items.
A link back to the meeting in mytranscript for the full recording and transcript.
The full transcript text is not copied into OTYS; the link provides access to it.
Which participants are matched
Only participants that are candidates or contacts in OTYS receive a note.
Colleagues (internal participants) are never synced. This is why correct internal domains matter (see "Organization settings and domains").
mytranscript matches a participant to an OTYS record by their email or an existing OTYS link. If no match is found, no note is written for that person.
When sync runs
Sync happens automatically when a meeting completes, and again whenever the summary or an action item is edited, so the OTYS note reflects the latest version. Users can also trigger a sync manually for a meeting or participant. If a sync fails for a temporary reason, mytranscript retries it automatically several times with increasing delays before giving up.
The controls available to you
As an administrator you can:
Maintain internal domains so the right participants are treated as colleagues versus candidates or contacts (see "Organization settings and domains").
Monitor sync health on the "Sync Dashboard" and in the OTYS sync logs (see "Logs and oversight"), and retry failed syncs.
Sync Dashboard
Administrators have a Sync dashboard that summarizes the health of OTYS syncing across your organization:
Counts of successful syncs, failed syncs, and pending retries.
An overall success rate.
A list of recent failures with the reason and a link to the affected meeting.
A Retry sync action for failed items.
For a detailed, filterable history of every sync, use the OTYS sync logs described in "Logs and oversight".
9.0 Calendar integration (Organization side)
Calendar integration in mytranscript is connected per user: each person links their own work calendar. As an administrator, your role is to understand how it works, encourage adoption, and set the organization-wide policies that decide what gets recorded from those calendars. This chapter covers the organization side.
How calendar integration works for your organization
Each user connects their own calendar (Google Calendar or Microsoft Outlook) from their personal settings. mytranscript only reads calendar events; it never modifies anyone's calendar. Once connected, a user's upcoming meetings appear in mytranscript and can be recorded automatically according to the recording rules.
For the user-facing steps to connect a calendar, see "Calendar integration" in the Regular User Guide. You can point users there.
What you control at the organization level
While the connection itself is per user, you control what happens with those calendar events through:
Organization-wide recording rules. These decide, across all connected calendars, which meetings are recorded or skipped. This is your main lever. See "Organization-wide recording rules".
Required versus optional rules. Mark rules as required where recording (or skipping) must be enforced for everyone, and optional where users may opt out.
Internal domains. These let rules distinguish internal from external attendees, which powers rules such as "Skip internal meetings". See "Organization settings and domains".
Bot configuration. The bot's name, join timing, and join message apply to every recorded calendar meeting. See "Bot configuration".
Seeing who has connected a calendar
In the Users tab, the user list shows a Calendar Connected indicator, and each user's detail view shows their calendar connection status. Use this to see how widely calendar integration has been adopted and to follow up with users who have not yet connected.
Encouraging adoption
Calendar integration is what makes automatic recording effortless. To get the most value:
Set sensible organization-wide recording rules first, so that once users connect their calendars, the right meetings are recorded automatically.
Ask users to connect their calendars during onboarding.
Keep internal domains complete so internal-only meetings are handled correctly.
What you cannot do
You cannot connect or disconnect a calendar on a user's behalf, and you cannot see the private contents of users' calendars. Calendar connection is a personal action each user takes from their own settings.
10.0 Logs and oversight
mytranscript keeps detailed logs so you can govern your organization, demonstrate compliance, and troubleshoot problems, especially OTYS sync. This chapter explains the three logs available to administrators and how to use them.
All three are found under Organization Settings.
Audit logs
The Audit Logs tab records significant actions taken in your organization, so you have a trail of who did what and when.
Each entry shows:
The date and the user who performed the action.
The action (for example, sign-in, meeting created or deleted, plan changed, recording rule changed, user blocked).
The resource affected and its type.
The originating IP address and whether the action succeeded.
You can filter by date range, user, action, resource type, and IP address, and export the results to CSV.
Use audit logs to answer questions such as "who deleted this meeting?", "when did this user become an admin?".
OTYS sync logs
The OTYS sync log (the Sync Logs tab) records every attempt to sync data to OTYS. This is your primary tool for troubleshooting why a meeting's notes did or did not reach OTYS.
Each entry shows:
The meeting and the participant involved.
The operation (for example, syncing a transcript note, or searching OTYS for a matching candidate or contact).
A link to open the candidate or contact in OTYS.
The status (Pending, Success, or Failed) and the timestamp.
You can expand an entry to see details, including the OTYS entity, the entity type (candidate or contact), and the request and response information for a failed sync. You can filter by date range, participant or meeting name, entity type, operation type, and status, and export to CSV.
Together with the "Sync Dashboard" (see "OTYS integration setup"), the sync logs let you see exactly which syncs failed and why, and retry them.
AI usage logs
The AI Usage Logs tab records each time AI was used in your organization, which is useful for oversight and cost awareness.
Each entry shows:
The timestamp and the meeting and meeting user involved.
The purpose (for example, speaker identification, or meeting summary and actions), including whether it failed.
The provider and token counts.
You can expand an entry to see more detail, including the custom instructions your organization applied to that request (the full underlying prompt is not shown). You can filter by date range, meeting user, and purpose, and export to CSV.
Using the logs together for governance
For an access or security question, start with Audit Logs.
For "the notes are not in OTYS" questions, use the Sync Dashboard and the OTYS sync logs.
To understand AI activity and the effect of your AI instructions, use the AI Usage Logs.
All three logs can be exported to CSV so you can keep records or share them with colleagues responsible for compliance.
11.0 Data, privacy, and retention
As an administrator you are responsible for how your organization handles meeting data. This chapter summarizes what you should know about retention, deletion, and the data shared with OTYS, so you can meet your privacy obligations.
What data mytranscript holds
For your organization, mytranscript stores:
Meeting recordings (video for online meetings, audio for in-person meetings).
Transcripts and AI outputs (summaries, action items, chapters, tags).
Participant details (names, emails, roles, and links to OTYS records).
User accounts and settings, and the logs described in "Logs and oversight".
Video retention
Video recordings are kept for a limited period and then expire automatically. How long videos are kept depends on your organization's plan. After a video expires:
The video is removed and can no longer be played.
The transcript and summary remain available.
mytranscript shows users when a video is about to expire or has expired. Encourage users to download a recording they need to keep before it expires.
Deletion and soft-delete
mytranscript uses soft-delete to support privacy and compliance:
When a meeting is deleted, it is removed from view. Deletion is handled in a way that supports data-protection requirements rather than being an instant, unrecoverable wipe.
Blocking a user preserves their meetings and history (so your records stay intact) while preventing them from signing in. See "User management".
If you have a specific data-deletion or data-subject request to fulfil, follow your organization's data-protection process and contact the service provider where platform-level action is required.
Data shared with OTYS
Because mytranscript writes meeting notes back to OTYS, you should be aware of what leaves mytranscript for OTYS:
For meetings with a candidate or contact, mytranscript writes a note to that person's OTYS record containing the summary, the action items, and a link back to the meeting.
The full transcript text is not written into OTYS; it stays in mytranscript and is reached through the link.
Colleagues are never synced to OTYS.
Once a note is in OTYS, it is governed by OTYS and your OTYS data-handling policies. Deleting a meeting in mytranscript does not automatically remove a note already written to OTYS.
You control which participants are treated as candidates or contacts versus colleagues through internal domains and participant types (see "Organization settings and domains").
Privacy good practices
Keep internal domains accurate so colleagues are not treated as external candidates or contacts.
Use the bot's join chat message to make recording transparent to participants (see "Bot configuration").
Use audit logs to review access and changes (see "Logs and oversight").
Apply the principle of recording only what you need by configuring recording rules thoughtfully (see "Organization-wide recording rules").
Where this guide stops
Platform-level data operations and infrastructure handling are managed by the service provider and are outside the scope of this administrator guide. For obligations that require action at that level, contact the service provider.
12.0 Admin troubleshooting and FAQ
This chapter covers the issues administrators are most likely to face, with a focus on OTYS sync failures and sign-in problems. For day-to-day user issues, see "Tips and troubleshooting" in the Regular User Guide.
OTYS sync issues
Meeting notes are not appearing in OTYS
Work through these checks:
Is the participant a candidate or contact? Colleagues are never synced. Check the participant's type on the meeting.
Does the participant have a matchable email? mytranscript matches participants to OTYS records by email or an existing link. Without a match, there is no record to write to.
Are your internal domains correct? A misconfigured domain can cause a candidate or contact to be treated as a colleague (and therefore skipped). See "Organization settings and domains".
Check the Sync Dashboard and sync logs. Look for the specific meeting and participant, read the failure reason, and use Retry sync. See "Logs and oversight".
A sync keeps failing
Open the entry in the OTYS sync logs and expand it to see the error and the response from OTYS. mytranscript retries temporary failures automatically several times. Permanent issues (such as no matching record, a missing email) are not retried automatically and need the underlying cause fixed. After fixing the cause, retry the sync from the dashboard or logs.
Sign-in (SSO) issues
A user cannot sign in from OTYS
Missing email in OTYS. If the user's OTYS account has no email address, sign-in cannot complete. Add an email to their OTYS user account and have them try again.
Account inactive or blocked. Check the user's status in the Users tab. Unblock them if appropriate. See "User management".
Wrong organization. If a user is told their account belongs to a different organization, their email is associated with another organization. Contact the service provider to resolve this.
Session expired. Ask the user to open mytranscript from OTYS again.
A user has no plan and cannot record
Assign them a plan from their user detail view, or set an organization default plan so new users are covered automatically. See "Plans, billing, and quota".
Email login codes are not arriving
The email must already be known to mytranscript (the user must have signed in via OTYS at least once).
Ask the user to check their spam folder.
There are limits on how often a code can be requested; ask the user to wait a few minutes before retrying.
Recording issues across the organization
Meetings are not being recorded automatically
Confirm the user has connected their calendar (the Calendar Connected indicator in the Users tab).
Review your organization-wide recording rules; a "Skip" rule or a missing "Record" rule may be the cause. See "Organization-wide recording rules".
Confirm the meeting has a video link; meetings without a link cannot be recorded.
Users report hitting their recording limit
Check their usage in the user detail view. Raise their plan if appropriate, or set expectations about the monthly allowance. See "Plans, billing, and quota".
Frequently asked questions
Do I create user accounts manually?
No. Users are created automatically when they first sign in through OTYS. You manage their access, role, and plan afterwards.
Does deleting a meeting in mytranscript remove the note from OTYS?
No. A note already written to OTYS is governed by OTYS. See "Data, privacy, and retention".
Can two administrators manage the organization?
Yes. You can grant the tenant admin role to multiple users. You cannot remove the role from yourself, which ensures the organization always has an administrator.
Where do I see the full prompt the AI used?
The AI usage logs show the custom instructions your organization applied, but not the full underlying prompt. See "Logs and oversight".
Who do I contact for platform-level problems?
For anything beyond your organization's settings (infrastructure, the SSO partner connection, or platform data operations), contact the service provider.