When your company or team rebrands:

1. Update your organization name to match the new brand
2. Notify team members about the name change
3. Update internal documentation referencing the old name
4. No code or API changes needed—integrations continue working

The new name reflects your brand while maintaining technical compatibility.

For organizations shared across teams that need clearer naming:

1. Change from generic names (e.g., "Team Project") to specific ones (e.g., "QA Vision Team")
2. Include department, region, or purpose in the name
3. Update the name as team structure evolves

Clear names help members quickly identify the right organization when switching between multiple organizations.

To standardize organization names across your company:

1. Establish naming conventions (e.g., "[Department] - [Purpose]")
2. Update existing organizations to follow the convention
3. Document the standard for future organizations

Consistent naming improves discoverability and organization.

To fix mistakes in the original organization name:

1. Navigate to General settings
2. Correct the spelling, capitalization, or formatting
3. Click Update to save

Simple corrections improve professionalism without technical impact.

Make organization names meaningful:

• Include team, department, or project context
• Use consistent capitalization and formatting
• Avoid abbreviations unless widely understood
• Keep names concise (under 50 characters recommended)

Example good names:

• "Manufacturing QA Team"
• "Retail Computer Vision"
• "Healthcare AI - Research"

Example unclear names:

• "Proj1"
• "test-org"
• "ABC123"

Notify members when renaming:

• Announce the name change in team channels
• Explain the reason for the change
• Update internal documentation and wikis
• Remind members that technical integrations are unaffected

Prevents confusion and ensures everyone recognizes the updated name.

Since organization IDs cannot be changed:

• Choose meaningful, permanent IDs when creating organizations
• Use lowercase, hyphens, and avoid special characters
• Follow your company's naming conventions
• Consider longevity—will this ID make sense in 5 years?

You can rename the display name anytime, but the ID is forever.

Create organization naming guidelines:

• Define standard formats for different team types
• Specify required or optional information (department, region, etc.)
• Document examples for reference
• Review and update conventions as needs change

Standardization scales as your company grows.

No. Organization IDs are permanent and cannot be modified after creation. They're used in:

• API endpoints and URLs
• Secret key configurations
• Vi SDK client initialization
• System integrations and webhooks

Changing the ID would break all these technical dependencies. If you need a different ID, create a new organization and migrate your resources.

Nothing—API calls continue working without any changes. Organization IDs (not names) are used in API requests, so renaming has zero impact on:

• Vi SDK scripts
• API integrations
• Webhooks
• Automation workflows

Your technical integrations remain functional.

No. URLs use the organization ID (which cannot change), not the organization name. All bookmarks, shared links, and documentation referencing URLs remain valid after renaming.

Example: https://vi.datature.io/org/acme-manufacturing/datasets stays the same regardless of organization name updates.

There's no limit on how often you can rename your organization. However, frequent changes can confuse team members. Best practice: rename only when necessary for clarity or rebranding.

No automatic notifications are sent to members when you rename an organization. It's your responsibility to communicate name changes to your team through:

• Team chat or email
• Internal announcements
• Documentation updates

Members will see the new name in the platform immediately, but proactive communication prevents confusion.

Organization names (display names) support most characters including spaces, hyphens, and symbols. However, organization IDs have stricter requirements (lowercase, hyphens only).

Recommended for names:

• Letters, numbers, spaces
• Hyphens and underscores
• Parentheses for context

Avoid:

• Excessive special characters
• Emoji (may not display consistently)
• Very long names (keep under 50 characters)

If you need a different organization ID, your only option is to:

1. Create a new organization with the desired ID
2. Migrate datasets, training projects, and models to the new organization
3. Update secret keys and API configurations
4. Remove members from the old organization
5. Add members to the new organization

This is a significant undertaking. Plan organization IDs carefully during initial creation.

For assistance with migrations, contact Datature support at [email protected].