---
title: "Organization Settings"
slug: "organization-settings"
updated: 2026-01-12T01:45:45Z
published: 2026-01-12T01:45:45Z
canonical: "learn.allspice.io/organization-settings"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://learn.allspice.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Organization Settings

## Organization Settings

Organization settings let you manage basic profile details, control who can see your organization, and configure permissions for repository access and team management. These settings apply to all repositories and members within an organization.

## Organization Profile

Use these fields to define how your organization is identified across AllSpice.

### **Organization Name**

The short, display name of your organization. **Example:** `AllSpice-Demos`

### **Organization Full Name**

A longer, descriptive name for formal identification. This field is optional.

### **Contact Email**

The primary email address where project notifications or inquiries should be sent. **Example:** `support@allspice.io`

### **Description**

A short summary of your organization's purpose or activity. **Example:** > A collection of demo repositories to help you learn AllSpice.

### **Website**

A link to your organization's home page or documentation site. **Example:** `https://learn.allspice.io`

### **Location**

(Optional) Add geographic or organizational location information.

---

## Visibility

Visibility determines who can see your **organization**, its **profile**, and its **public repositories**. This setting does *not* override individual repository privacy settings, but it does define the baseline discoverability of the organization itself.

### **Public**

Your organization is visible to anyone, including: - Visitors browsing `hub.allspice.io` - Users without an account - Search engines (if enabled)

Use this if you want your organization to be discoverable---for example, open-hardware groups, public demo repositories, or educational projects.

### **Limited** *(Visible to authenticated users only)*

Only logged-in users on the server can view your organization. This is useful for semi-private ecosystems, internal communities, or when you want discoverability among users but not anonymous visitors.

### **Private** *(Visible only to organization members)*

Your organization is completely hidden to everyone except members. Choose this for: - Confidential or proprietary hardware projects

- Organizations that do not want to appear in searches
- Environments where privacy and access control are critical

---

## Permissions

### **Repository Admin Team Access**

This setting allows repository administrators within the organization to:

- Add teams to repositories
- Remove team access from repositories

Enable this when you want decentralized access management, especially in large engineering teams or organizations with many repositories.

See [Invite people to your team](/v1/docs/how-to-invite-or-add-people-to-your-organizations-teams) or [team management](/v1/docs/how-to-configure-teams).

---

## Organization Avatar

You may upload a custom avatar to visually identify your organization.

- Click **Choose File** to select an image
- Click **Update Avatar** to save it
- You can also remove the existing avatar using **Delete CurrentAvatar**