cables DocumentationHow To UseWorking with filesKeyboard ShortcutsUser Interface WalkthroughBeginner TutorialBeginner 1: Drawing A CircleBeginner 2: TransformationsBeginner 3: ColorMore TransformationsIntermediateImage CompositionsPost-Processing 3D ScenesExporting And EmbeddingHow to serve files externally and fix CORS headersExporting PatchesExport using the cables command line interfaceExport via IframeExport creating a standalone executableExport to github (pages)Export and deploy to netlifyExport full PatchExport a ZIP fileExternal triggers / functionsUsing variablesPreviewing / uploading exported cables patchesExamples for EmbeddingPermissionsUsersPatchesTeamsOpsMultiplayerPatchlistsCoding OpsCreating AttachmentsGeneral op/Port CallbacksPortsMultiPortsArray PortsBoolean portsInteger Number PortsObject PortsString portsTrigger PortsFloating Point Number PortsGUI/UI attributesHello Op - Part 1LibrariesDeveloping OpsRenaming / Creating a new versionCreating Viz OpsGuidelinesObject PortsPatching Ops / SubPatchOpsWriting ShadersWeb Audio Op DevelopmentDeveloping CablesRepositoriesSet up local environmentScriptsHow to work with forksGenerated DocumentationUsing standalone to develop cablesCables StandaloneGeneralCoding OpsSharing opsUsing NPMImport/ExportStandalone - FAQLightingLightsShadowsWorking With AudioBasic Audio SetupWorking with EffectsReal-Time Audio Analyzation & Audio VisualizationOffline Audio Visualization & AnalyzationCommunicationcables APIOptimizing Performance In PatchesTools for debugging your patchHow to optimize cables patches with the Performance opHow to optimize cables patches with the ProfilerCommon pitfalls with the "usual suspects"Optimizing arraysDebugging Shaders with ShaderInfoFAQAudio in web browsersHow to make demoscene demos with cables.glEmbeddingHow to integrate my cables patch into my CMS (webflow/wix/squarespace/...)?How to remove grey rectangles on touch (mobile)?Why doesn't the DownloadTexture op work on iOS?How to disable page scrolling on mobile?Mobile tippsHow to run exported patches on your local machineTransparent CanvasFeatures and SupportHow to contribute code to cablesWill there be support for (animated) GIFs?Can i use a website as a texture?Screenshots and Video recordingHow to report a bug in cablesHow can I share a patch to get help?How can I support cables?Video playback in cablesGeneral questionsWhat is dev.cables.glHTML And CSS In CablesJavascript Frameworkscordova / phonegapelectronreactvuejsLicenses and paymentWhat license do i need to use cables?Will I have to pay for it in the future?How is my work licensed when using cables?Does cables support midi and OSC?Patch PermissionsMy User Profile & Social MediaShadertoyCables at schools and universitiesTechnical questionsWebGL1 and WebGL2
cables Documentation  ⟩  Permissions  ⟩  Teams

Teams

Cables allows to create teams to share ops and patches with other users or the whole community.

Users can join a team by either being invited to it by other members, requesting access to the team or simply joining public teams on their own.

Button

Access-Level

Non-Member

Any user that is not a member of a team already, can:

  • View the teams page for unlisted and public teams
  • See a list of public patches for unlisted and public teams
  • See a list of the ops provided by the team
  • Join public teams
  • Request access to unlisted teams

Read-Only

Any team member with "Read Only" permissions additionally can:

  • View the teams page with all public and private patches
  • Use the ops provided by the team in ALL their patches
  • Request full access to the team
  • Leave the team

Full-Access

On top of the above, any team member with "Full Access" permissions can:

  • Invite users to the team
  • Remove users from the team
  • Grant "Full Access" to members of the team
  • Add patches to the team
  • Add and edit team-ops
  • Change the teams settings (logo, name, description, visibility, op namespaces, ...)

Owner

Once you create a team on cables.gl you will become the owner of this team. As a team-owner you can:

  • Delegate ownership of the team to some other member

Visibility

Teams itself have three levels of visibility: "public", "unlisted" and "private".

Public teams will be:

  • Listed on the public teams page
  • Joinable by any registered cables user without approval by the team-owner (they will get "Read Only" access)
  • Linked on the patch page for patches that added the team

Unlisted teams will be:

  • Accessible to non-members that know the URL of the team
  • Show a "Request Access" button on the team page
  • Show only public patches to non-members on the team page
  • Linked on the patch page for patches that added the team only for members

Private teams will be:

  • Accessible only by members, invite people to add them to the team
  • Linked on the patch page for patches that added the team only for members

Sharing patches

To share patches with a team, you need both "Full Access" on the patch and on the team. Add the team on the "Collaboration" tab in the settings of the patch in question.

Sharing ops

To share ops with a team, register a op namespaces for your team in the teams settings (needs "Full Access") and create an op in this namespace in the editor. If you have other ops already and want to move them to the team, simply use the op rename feature to move them to a new namespace.

Found a problem? Edit this file on github and contribute to cables!