Skip to main content
Organization profiles enable companies, nonprofits, and groups to establish a structured presence on Aya with team management and role-based permissions.

​
What are Organizations?

Organizations are a special profile type designed for:
  • Companies and businesses
  • Nonprofits and NGOs
  • Open source projects
  • Educational institutions
  • Community groups
  • Any structured entity with multiple members
Unlike individual profiles (one per user), you can create and manage multiple organization profiles.

​
Creating an Organization

1

Navigate to create profile

From your dashboard, select “Create New Profile”
2

Choose 'Organization' type

Select organization from the profile type options
3

Set basic information

  • Slug: Your organization’s unique URL identifier
  • Title: Official organization name
  • Description: Brief overview of your organization
  • Profile Picture: Logo or brand image
  • Default Locale: Primary language for content
4

Configure features

Enable or disable modules:
  • Relations (member/contributions display)
  • Links (social media/platforms)
  • Q&A (community questions)
  • Discussions (comments on profile)
5

Create organization

You are automatically set as the owner (Level 7 access)

​
Organization URL Structure

Organizations use the same URL pattern as all profiles: 
https://aya.is/{locale}/{org-slug}
Example: 
https://aya.is/en/acme-corp
https://aya.is/ja/acme-corp

​
Team Management

Organizations can create teams to structure their members:

​
Creating Teams

1

Navigate to organization settings

Access your organization’s admin panel
2

Go to 'Teams' section

View existing teams or create new ones
3

Create new team

  • Name: Team identifier (e.g., “Engineering”, “Marketing”)
  • Description: Optional team purpose
4

Assign members to teams

Add existing organization members to the team

​
Team Features

  • Member Grouping: Organize members by department, project, or role
  • Resource Assignment: Assign repositories, links, or other resources to teams
  • Member Count: Automatic tracking of team size
  • Resource Count: Track resources assigned to each team
  • Filtered Views: Filter membership lists by team
Use teams to create project-based groups (“Mobile Team”, “Web Team”) or functional groups (“Core Contributors”, “Documentation”).
Teams cannot be deleted if they have active members or assigned resources. Remove associations first.

​
Member Management

Organizations use the same 7-tier membership system as all profiles:

​
Membership Levels

Follower (Level 1)

Basic following, no editing rights

Sponsor (Level 2)

Financial supporters, view sponsor content

Member (Level 3)

Active participants, member content access

Contributor (Level 4)

Can create content, add resources

Maintainer (Level 5)

Moderate content, manage members

Lead (Level 6)

Strategic decisions, team management

Owner (Level 7)

Full administrative control

​
Adding Members Directly

Who can add members:
  • Owners (add any level)
  • Leads (add up to maintainer level)
  • Maintainers (add up to contributor level)
1

Search for user

Use email or profile search to find the user
2

Select membership level

Choose appropriate role (follower through owner)
3

Assign to teams (optional)

Add member to one or more teams
4

Set dates (optional)

  • Started At: When membership begins
  • Finished At: Expiry date for temporary roles
5

Add member

Member immediately gains access based on role

​
Referral-Based Membership

Organizations can use the referral system for community-driven growth:
1

Member creates referral

Existing member nominates a candidate profile (must be individual profile)
2

Voting period begins

  • Status: voting
  • Members vote with scores 0-4
  • Optional comments on votes
  • Average score calculated
3

Voting concludes

  • Accepted: Average score meets threshold, invitation sent
  • Rejected: Status changes to reference_rejected
  • Frozen: Moderators pause voting for review
4

Candidate responds

  • Accepts: Becomes member with assigned level
  • Rejects: Status set to invitation_rejected
  • Ignores: Invitation remains pending
Referrals can only be created for individual profiles. Organizations cannot refer other organizations.

​
Membership Properties

Each membership can store custom properties (JSONB):
  • Job title
  • Expertise tags
  • Project assignments
  • Custom metadata

​
Publishing Stories as Organization

Organizations can publish content:
1

Create story

Author creates story with their individual profile
2

Publish to organization

Select organization profile as publication target (requires contributor+ access)
3

Set publication type

Choose story kind for this publication (article, news, announcement, etc.)
4

Feature (optional)

Mark as featured to highlight on organization profile
A single story can be published to multiple organizations, allowing cross-posting for shared initiatives.

​
OAuth Integration

​
GitHub Organizations

Link GitHub organization accounts:
1

Initiate OAuth flow

Click “Link GitHub” on organization profile
2

Authorize with GitHub

Grant read:org and public_repo permissions
3

Select organization

Choose which GitHub organization to link (from organizations you admin)
4

Profile link created

  • GitHub profile link added with verified badge
  • Repositories automatically synced
  • Organization avatar synced
Synced Data:
  • Organization profile information
  • Public repositories as resources
  • Repository stats and activity
  • Organization members (optional)

​
LinkedIn Organization Pages

Link LinkedIn company pages:
1

Initiate OAuth flow

Click “Link LinkedIn” on organization profile
2

Authorize with LinkedIn

Grant organization page permissions
3

Select organization page

Choose from company pages you manage
4

Profile link created

LinkedIn page linked with verified badge

​
Resources Management

Organizations can link external resources: Resource Types:
  • GitHub repositories (auto-synced or manual)
  • External links
  • Documentation sites
  • Project pages
Resource Features:
  • Assign resources to teams
  • Track who added resources
  • Resource descriptions
  • Custom properties (JSONB)
1

Add resource

Navigate to organization’s resources section
2

Select resource type

Choose GitHub repo sync or custom link
3

Configure resource

  • Title and description
  • URL (if custom link)
  • Remote ID (if managed sync)
4

Assign to teams

Select one or more teams (optional)
5

Save resource

Resource appears on organization profile

​
Custom Pages

Organizations can create custom pages:
  • About: Company history and mission
  • Team: Leadership and member highlights
  • Careers: Job opportunities
  • Press: Media and press releases
  • Legal: Terms, privacy, policies
Page Visibility:
  • Public (listed in nav)
  • Unlisted (direct link only)
  • Private (contributors+ only)

​
Visibility Controls

Control who sees each link:
  • Public: Everyone
  • Followers: Followers and above
  • Sponsors: Sponsors and above
  • Members: Members and above
  • Contributors: Contributors and above
  • Maintainers: Maintainers and above
  • Leads: Leads and above
  • Owners: Owners only
Use Cases:
  • Public: Main website, social media
  • Members: Internal wikis, member portals
  • Contributors: Code repositories, design files
  • Owners: Admin panels, financial dashboards

​
Module Visibility

Control feature visibility:
  • Public: Shown in navigation, visible to all
  • Hidden: Enabled but not in nav (direct access)
  • Disabled: Completely disabled (404)

​
Organization Settings

​
Profile Features

{
  "feature_relations": "public",    // Members/contributions visibility
  "feature_links": "public",        // Links module visibility  
  "feature_qa": "hidden",           // Q&A module visibility
  "feature_discussions": "public"   // Discussion module visibility
}

​
Story Defaults

{
  "option_story_discussions_by_default": true
}
When enabled, all new stories published to this organization have discussions enabled by default.

​
Organization Permissions

​
Who Can:

  • Anyone (public content)
  • Appropriate membership level (restricted content)
  • Owners
  • Leads (limited fields)
  • Admins (global)
  • Owners (all members)
  • Leads (up to maintainer level)
  • Maintainers (up to contributor level)
  • Owners
  • Leads
  • Contributors and above
  • Story author must have contributor+ membership
  • Contributors and above
  • Can add/remove resources
  • Assign resources to teams

​
Best Practices

  • Create teams based on function (Engineering, Design, Marketing)
  • Or based on projects (Project Alpha, Project Beta)
  • Keep team names clear and descriptive
  • Use team descriptions to clarify purpose
  • Regularly review team membership
  • Start new members as followers or members (Level 1-3)
  • Promote to contributor+ after proven engagement
  • Reserve maintainer+ for trusted long-term members
  • Use referral system for community-driven growth
  • Document membership criteria publicly
  • Publish regular updates as stories
  • Use announcements for important news
  • Create custom pages for evergreen content
  • Feature key stories on organization profile
  • Enable discussions for community feedback
  • Keep main links and pages public
  • Use member-only content to reward engagement
  • Hide admin/internal links from public
  • Consider sponsor-only content for funding

​
Next Steps

Communities

Learn about community-focused profiles

Teams & Members

Deep dive into team management

Stories

Publish content as organization

Custom Domains

Set up custom domain for your organization

Build docs developers (and LLMs) love

Get started for freeTalk to us