Meetin.gs profile and branding settings

Short answer: Set your name, photo, description, colors, links, and default zone. Begin with “Set the public name, role, description, and reliable contact context.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

Set the public name, role, description, and reliable contact context.Start with the intended outcome and the record that controls it.
Choose a default time zone and verify its daylight-saving behavior.Review every related setting before saving so one rule does not mask another.
Use an accessible image and colors with sufficient contrast.Keep private data and guest-facing information clearly separated.
Open every public event page to check inherited profile changes.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot Meetin.gs profile settings

These are the failures reported most often for this specific task, with the cause that explains each one.

Profile changes are not showing publicly.

Public pages inherit the profile, so open one in a signed-out session. Cached organizer views are the usual explanation.

My name renders differently to invitees.

Set the public display name deliberately rather than inheriting it from the sign-in account.

Are my brand colors accessible?

Check contrast against the background. A booking page that cannot be read on a phone in daylight loses bookings regardless of its palette.

Related Meetin.gs help

Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.

Meetin.gs profile and branding settings acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. Set the public name, role, description, and reliable contact context.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Choose a default time zone and verify its daylight-saving behavior.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Use an accessible image and colors with sufficient contrast.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Open every public event page to check inherited profile changes.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

Evidence type

What to record

Controlling input

The account, event type, setting, public link, and time zone used in the test.

Participant result

The exact choices, context, confirmation, or error visible while signed out.

Lifecycle result

What changes after confirmation, finalization, cancellation, reschedule, or retry.

Failure boundary

The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.

Owner

The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

Custom event types

Create focused templates for discovery calls, interviews, office hours, reviews, workshops, and recurring conversations. This page explains custom event types requirements. Confirm production availability before depending on this capability.

Review scope

Meetin.gs profile and branding settings: frequently asked questions

Short answers to the questions organizers ask most about Meetin.gs profile settings.

What does the profile control?

The public name, role, description, image, colors, and default time zone that every public event page inherits.

Why do my changes not appear publicly?

Public pages are inherited, so check one in a signed-out session. A cached organizer view is the usual explanation.

Which time zone should I set?

The city you actually work from, as a full IANA identifier. That keeps daylight-saving transitions correct without any manual adjustment.

Do brand colors matter for bookings?

Contrast does. A booking page that cannot be read on a phone in daylight loses bookings regardless of how well the palette matches your brand.