LogoLogo
  • Overview
    • Introduction
      • Git-Based Source Control
      • DeviceLink
    • System Requirements
    • Supported Vendors and Device Types
    • Glossary
  • Git-Based Source Control
    • Getting Started
      • Planning
      • Initial Setup
        • Migrations
    • Basic Tasks
      • Navigation
        • Home page
        • Exploring the Web App
        • Exploring the Desktop App
      • Configuration
        • Creating Repositories
        • Creating Templates
        • Cloning Repositories
      • Operations
        • Pulling
        • Committing
        • Pushing
        • Managing History
        • Binary & Large Files
    • Advanced Tasks
      • Branching
        • Branch Protections
      • Pull Requests & Code Review
        • Contributors
        • Reviewers
      • Merging
    • Additional Features
      • Topics
      • Issues
        • Milestones
        • Labels
        • References and Links
      • Wiki
      • Tags & Releases
      • Webhooks
      • Activity
    • Administration
      • Org Settings
      • User Management
        • External Identity Management (SSO + SCIM)
      • Teams & Permissions
        • Permissions by Account Type
      • Registration & Billing
      • Repo Settings
      • Desktop App Options
      • Profile and Settings
        • Notifications
        • Two-Factor Authentication (2FA)
    • Supported Vendors
      • ABB
      • Beckhoff
      • B&R Automation
      • CODESYS
      • Inductive
      • Lenze
      • Rockwell
        • RSLogix 500
        • RSLogix 5000
        • Studio 5000 Logix Designer
      • Schneider
        • Control Expert
        • Machine Expert
      • Siemens
        • Siemens Step7 TIA Portal
        • Siemens Step7 5.x
      • WAGO
    • Integrations
      • Discord
      • Jira
      • Microsoft Teams Connectors
      • Slack
      • Zapier
      • Microsoft Teams Workflows
  • DeviceLink
    • Getting Started
      • Architecture
      • Planning & Installation
    • Sites and Agents
      • Sites
        • Site Settings
        • File Lists
        • Graphs and Metrics
      • Agents
        • Creating a Site-Based Agent
        • Creating a Multi-Site Agent
    • Projects and Devices
    • Vendor Configuration
      • Beckhoff TwinCAT 3
      • CODESYS v3
      • Copia FTP
      • Copia sFTP/SCP
      • Copia Scripting
      • FANUC Robots
      • Rockwell RSLogix 500
        • Smart Filter
      • Rockwell Studio/RSLogix 5000
        • Smart Filter
      • Rockwell PanelView ME HMI
      • Schneider Control Expert
      • Siemens Step7 TIA Portal
      • Siemens Step7 5.x
    • Jobs
      • Job Navigation
      • Creating Jobs
      • Managing Jobs and History
      • Manual Backups
      • Pull Requests
    • Additional Features
      • Webhooks
      • Copia Import Tool
        • Getting Started
        • Preparing your data
        • Importing your data
        • Rolling back a prior import
    • Administration
      • Teams
      • Permissions
      • Notifications
  • Copilot
    • Copia Copilot
    • Getting Started
    • Using Copia Copilot
  • Copilot FAQ
  • Support
    • Best Practices
    • FAQs
      • Git-Based Source Control
        • Troubleshooting
      • DeviceLink
        • Troubleshooting
Powered by GitBook
On this page
  • Single-Role Teams
  • Single-Role Teams FAQs

Was this helpful?

  1. Git-Based Source Control
  2. Administration

Org Settings

PreviousAdministrationNextUser Management

Last updated 2 months ago

Was this helpful?

Organization settings are accessible for organization owners from the Dashboard, by clicking on the gear icon of the organization icon. The settings are broken out into four areas.

  1. (for Organizations) are covered in the section of the documentation.

  2. are explained under the Issues section of the documentation.

  3. is covered in a separate section

  4. are covered in a separate section.

The rest of the organization-level options are described as follows:

You can add or modify the organization name, full name and description.

If there is a related website or location, you can add this, as well.

The Permissions setting, if checked, allows admins of a repository to give team access to their repository only.

Your organization's avatar can be customized, if desired.

Single-Role Teams

By default, this setting is disabled, allowing team administrators to set different permission levels for individual members within the team.

Single-role teams do not require all teams to have the same permission level. For example, it would be reasonable to have one Technicians team with all of your organization's Read users, and another Controls team with all of your organization's Write users.

Single-role teams apply the same permission level to all users in a team. However, users can have different permissions on other teams. For example, a user can be a Writer on the NewYorkWriters team, and a Reader on the DetroitReaders team.

The team's role is set during team creation and applies to all members. Organization owners can modify the role for a team in the team settings panel:

Single-Role Teams FAQs

What happens to permissions when single-role teams are first enabled?

When single-role teams are first enabled, all teams besides the Owners team will be set to Read access. Owners can then go through each of the teams and set the appropriate access level for each team.

What happens if I start using single-role teams, and disable it later?

In this case, users will revert to whatever more-granular permissions they had before you enabled single role teams. An illustrative example follows:

  1. Owner creates Team A, with User 1 set to Write, and User 2 set to Read

  2. Owner enables single-role teams:

    1. Team A is set to Admin access.

    2. User 1 and User 2 have admin access to all of Team A's resources.

  3. Owner disables single-role teams

    1. User 1 reverts to Write access for Team A, and User 2 reverts to Read access for Team A

If enabled, within a given team, every member of the team has the same for that team (Read, Write, or Admin). The single-role requirement applies to all teams in your organization.

When using Single-Role teams, you can also set up with to maximize access control of Copia resources from your external Identity Provider. With both of these features enabled, you can control a user's access level in Copia simply by assigning them to a group in your Identity Provider.

permission level
Webhooks
Additional Features
Labels
External Identity Management
Multi-Site Agents
Team Mapping
SAML Assertions or Directory Sync
The Team Settings view, with the Team Access Mode (Role) highlighted
The Team view with the Team Settings button highlighted