Copium Teams

A team is a group of Copium accounts with a shared library. The Copium Teams plan gives every member Copium+ while they are on the team. See Your account and plans for the plan itself. This page covers who owns what and who can do what.

Where things are

Open Teams in the top bar. Each team on that page has tabs: Overview, Members, Library & sharing, Permissions, Integrations, Evidence and Stats. Which tabs you see depends on what your role allows in that team:

• Everyone sees Overview (on a team without the Teams plan, with its storage; on a team with the plan, owners and admins see the Need more storage? form), Members and Library & sharing.
• Permissions is for the owner only. See Changing what members can do.
• Integrations (the Discord activity feed and team keys) shows for anyone who may change team settings or manage team keys.
• Evidence is for the owner and admins.
• Stats shows for anyone who may see team stats.

Use the arrow keys, Home and End to move between the tabs. Under the tabs, Leave team is for everyone but the owner. The owner sees Transfer ownership and Delete team instead (see Transfer ownership and Delete a team). The team library page is described under "What a team owns" below. Putting one of your own items in a team is done on the item's own screen with Add to team, not on the Teams page: see Adding something to a team.

What a team owns

An upload, album, media board, meeting poll, short link, Drop file, Discord preview template or collection is team-owned when:

• it is created in the team (see Making something in a team),
• you add it to the team with Add to team (you must confirm that the team will own it and decide what happens to it), or
• it is an upload sent with a team key. Text files, pastes and HTML transcripts sent with a team key are uploads too, and belong to the team the same way. Only uploads made with a team key since team ownership arrived (November 2026) belong to the team. Earlier team-key uploads stay with their uploader, and that includes any text files, pastes and transcripts sent with a team key before this change: they were saved as the key maker's own.

The person who made it is shown as its creator, but that gives them no special rights. What anyone can do with a team-owned item comes from their role in the team. If the creator leaves the team, they have no rights over it at all.

Uploads and albums you only shared to the team library (a personal upload that is "shared with the team") stay yours. Leaving takes uploads you only shared to the team library out of it. Albums you shared with the team stay shared until you take them out.

A team can also show a Discord calendar. A calendar is never owned by the team: it stays with the member whose Google connection it uses.

The team's items can be listed by kind (uploads, albums, boards, polls, links, drops, Discord preview templates, calendars and collections) with the API. All kinds are also on the team library page (Teams, then Open team library), collections included: they have their own Collections tab, and a collection card opens the collection in the same tab. A team's collections can also be opened from Collections (/collections?team=<id>). See The team library page and The team's items list.

The team library page

Open Teams, then Open team library on a team. The page has one tab per kind: Uploads, Albums, Boards, Polls, Links, Drops, Discord previews, Calendars and Collections. Each tab shows how many items of that kind the team has. Use the arrow keys, Home and End to move between the tabs. A tab's address ends in ?type= followed by the kind (for example ?type=board), so you can bookmark it or send it to another member.

• Search this tab finds items by their title (on the Uploads tab also the file name and the text in screenshots). The Members list narrows a tab to what one member made. Each tab shows 60 items at a time; Load more shows the next 60. A line beside the filters reads out how many items are listed (for example "60 shown", or "60 shown, more available" while Load more has more), so screen readers announce it after a search.
• Each card shows the item's title, a short description of it, Created by the member who made it and, when someone else put it in the team, Added by. Team-owned marks items the team owns. Shared marks items still owned by the member who shared them. Locked marks a locked board or a team-only upload. An upload made with Clink also has a Clink label ("Uploaded with Clink" to screen readers), protected uploads included.
• A protected upload (one with a password, delete after viewing or an expiry that has passed) shows a lock and Protected - open its page instead of a picture. Open its page to see it.
• Open goes to the item's own page and Copy copies its public link, where it has one. On a collection card, Open and the title open the collection in the same tab, and there is no Copy, because a collection has no public link; its card says how many items it holds and Updated with the date. Copium staff visiting a team see "Staff can't open collections" instead of Open on those cards. Comments opens the team's comments on an upload. If the team's roles don't let you comment, or you are visiting as Copium staff, the comments are read-only and the comment box is hidden. The comment count is refreshed each time you open the comments. Add to collection is on every card except a collection card (a collection can't hold another collection), and Copium staff visiting a team don't see it. It opens the dialog described in Add to collection; if you may add to the team, that dialog's New collection in (team name) makes a collection the team owns. For a shared upload that is protected (password, burn after viewing or expired), the button is New collection and makes a personal collection.
• Take out and Delete for good show only when the team's roles allow you to use them on that item. Both ask first. Take out says where the item goes: a team-owned item goes back to the member who made it; an item that was only shared with the team stays with them. On a calendar the button, the dialog and the confirmation say Stop showing instead, and the calendar stays with the member who connected it. Delete for good can't be undone. If Copium refuses, the dialog stays open and shows the reason, for example one of the messages under Deleting a team item.
• New (when you may add to the team) opens a menu of places where you can make something for the team: Board, Poll, Short link, Drop, Album, Collection, Discord preview template and Calendar (a calendar to show). Each opens the matching page with the team in its address (?team=). The page says Creating in (team name) with a link Back to the team library (a calendar's Add a calendar form says Showing in (team name)). See Making something in a team. Uploads are not in this menu: they join a team with Add to team or a team key.
• Copium staff can open any team's library to look but can't change anything. The page says so, and each visit is logged.

Making something in a team

You make something in a team from inside the team: open the team's library and press New. There is no list on the create pages for choosing who owns something. A page opened from New says Creating in (team name), with a link Back to the team library, above the form: Media boards (next to New board), Albums, Find a time to meet (above Create poll, signed in only), Links (for one link and for Shorten many at once), Copium Drop, Collections (above Create collection), and Save as new in the saved templates of the Discord profile & server preview. On Google Calendar for Discord, a new calendar says Showing in (team name) instead, because a calendar is shown in a team, never owned by it (see Calendars shown in a team). Opened on its own, without a team, each page makes your own, as before. New is only there when you may add to the team.

• Under Creating in (team name) there is a short note, for example for an album: "(team name) will own this album. The team's owner decides who can rename, share or delete it." Boards, polls, links, drops, templates and collections say the same with their own name ("this board", "these links" for many at once). For a calendar it says "Everyone in (team name) will see its name, server, last sync and how many events are coming. It stays yours."
• The team comes from the page's address (?team=), and it stays there, so reloading the page keeps the team (as does switching between Shorten many at once and one link). The page reads your teams when it opens, so if you lose the right to add to the team afterwards, the page notices after a reload; until then Copium refuses what you make with its usual reason. An address with ?team= for a team you can't add to (a deleted team, a right you lost, or an id that isn't a team) is ignored once your teams are loaded: no Creating in line is shown, a muted line says "You can't add to that team, so what you make here is yours.", and what you make is your own. The address can't carry two ?team= values; that counts as no team. There is no way to change to another team on the page: go back to that team's library and press New there. To make something that is yours, open the page without ?team=.
• What you make then shows Owned by (team name) and is in the team library. Whatever you make on a page opened without a team is yours, as before.
• If Copium refuses (for example your role can't add to the team, the team is full, or Copium+ is needed), you see its reason exactly as it words it, and nothing is made. The messages are in each kind's section below.
• A drop made in a team has a download limit only when your role there may both change who can see items and delete them. Otherwise the Download limit box is turned off and says "Your role in (team name) can't set a download limit". A number you had typed in the box is kept while you are creating in that team and comes back if the team goes away. The Creating in line, its note and this note are shown in your language.
• A link made in a team can only be on the site's own domains, so your own subdomain and domains aren't offered while you are creating in a team.
• Uploads aren't made in a team on the Upload page: they join a team with Add to team or a team key.

Adding something to a team

Press Add to team on one of your own items. It shows only for an item no team owns yet, and only when you are in a team whose roles let you add to it. Where to find it:

A dialog opens with Cancel in focus. Its title is Add "(item name)" to (team name)? If more than one of your teams lets you add, a Team list lets you choose. The dialog says:

(team name) will own "(item name)". Everyone in the team can see it. What members can do with it is up to the team's owner (by default, the owner and admins can change its sharing, take it out or delete it). You won't be able to delete it yourself or take it back unless your role allows it. If you leave the team or delete your account, it stays with the team.

Under that, one short line says what changes for that kind of item: an upload's link keeps working for anyone who has it unless someone makes it team-only (or, if the team's library is team-only, it becomes team-only); an album's invite link stops working and the people who joined stay; a board's invite link stops, it becomes team-only, its display link gets a new address and its Discord picture stops; a poll's organizer link keeps working for changes, but deleting the poll or hiding its answers needs a signed-in team role; a link's expiry, click limit, password and start time stay; a drop still expires on its date; a template's share link, if it had one, is replaced by a new one that only people who may change sharing can see; a collection can be opened by everyone in the team, and each person sees only the things in it they can open. The dialog also lists up front what Copium is going to refuse for this item, in Copium's own words: an upload that has an expiry, delete after viewing or a password, and a drop that has a download limit. The button stays available. When your role in the team lets you both take items out and delete them, it adds "Your role in (team name) lets you take it out again or delete it."

Tick I understand (team name) will own it. and press Add to team. The button is always available: if you press it without ticking, focus moves to the box and it says "Tick the box to confirm". While it works the button says Adding. When it is done you see "Added to (team name)", the dialog closes and the item shows Owned by (team name). If Copium refuses, the dialog stays open and shows the reason exactly as Copium words it (see the list below).

An upload or album you shared with one team's library can only be added to that team. The dialog then has no Team list and says "It's shared with (team name), so it can only go to that team."

Showing a calendar is different, because nothing is given away. Show in team opens Show "(calendar name)" in (team name)?: "Everyone in (team name) will see its name, server, last sync and how many events are coming. It stays yours: its Discord settings stay with the server's calendar admins, and you or the team's owner or admins can take it out." There is no box to tick, and the button is Show in team. You see "Shown in (team name)".

Who owns what

Items show who owns them, in words and an icon, never by colour alone:

• Owned by (team name): the team owns it. On a team album, Created by (name) says who made it, or Deleted member when that account is gone.
• Shared with (team name): still yours, only shared with the team (an upload or older album you shared with its library).
• Shown in (team name): your calendar, which the team shows but doesn't own. Stop showing takes it out again.

You see these on the items of every kind: the upload grid (and Owned by in its side panel), the albums list and album page, the boards list and board page, a poll's page, the rows of links, drops and templates, and the calendar cards. An item a team owns shows only the buttons the team's roles let you use: for example Edit, Off/On and Delete on a short link, Delete on a drop, an album or an upload, the results visibility and Delete poll on a poll, Rename, Delete and the share link of a template, and the title of an upload. The quick-share list and Team only box of an upload are for your own uploads only. When you edit a team link, only the fields you changed are sent, and fields you can't change (the limits, password, start time and domain when you may not change sharing) are greyed out.

Add to team only works while you are signed in on the website (an API key or team key gets "Sign in on the website to do this"). It is refused when:

• your role can't add to the team (the owner switched Add to the team off for members): "Only the team owner or admins can do that"
• the upload has an expiry or delete after viewing: "Remove its expiry and burn-after-viewing first - team items only expire when someone allowed to change limits sets that"
• the upload has a password: "Remove the password first - a team admin can add one after"
• the item already belongs to another team: "That belongs to (team name) already"
• the item is shared with another team's library: "It's shared with (team name) - take it out of that library first"
• the team's storage is full (see Storage)
• the upload is held as locked evidence
• the poll was made without signing in, or isn't yours: "Item not found" (a poll needs an account behind it to be added)
• the board isn't yours: "Item not found"
• the team already has 200 boards: "(team name) can have up to 200 boards"
• the calendar is already shown in another team: "It's shown in (team name) - take it out there first"
• the short link was blocked: "Blocked links are kept for review and can't be added to a team"
• the short link is on your own subdomain or domain: "Links on your own domain can't be added to a team - move it to one of the site's domains first". Change its domain to one of the site's own first (Edit). Copium never moves it for you.
• the drop has a download limit: "Drops with a download limit can't be added to a team - send it again in the team"
• the drop has expired or been removed, or isn't yours: "Item not found"
• the team's drop pool is full (50 drops or 20 GB with the Teams plan, 10 drops or 2 GB without it; see Drops in a team)
• the template isn't yours: "Item not found"
• the team already has 50 templates: "(team name) can keep up to 50 templates - delete one first"
• the pictures a template would bring along don't fit in the team's storage (see Storage)
• a collection when the team already keeps as many as it can, holds more things than the team's collections can, or holds things the team doesn't have: see Collections for the messages

Adding an album stops its old invite link. Contributors stay. A team album can't be shown on a personal profile.

Adding a board stops its old invite link, the same way. People who already joined by it stay. The board's other links stop too: it becomes team-only, its display link gets a new address if it had one (the old one stops working), and its Discord picture stops. See Media boards in a team.

Adding a Discord preview template stops its share link: if it was shared, it gets a new link that only people who may change sharing can see. The pictures only that template uses come along and become the team's. See Discord preview templates in a team.

Adding a short link keeps its expiry, click limit, password and start time. Adding a poll doesn't change its organizer link. If a signed-in request leaves out the confirmation when showing a calendar, you see "Confirm that you want to show it in the team". The website always sends it.

Roles and permissions

Every team has one owner, any number of admins, and members. The owner can always do everything.

Setting an expiry or delete after viewing on a team upload, or a download limit on a team drop, needs both the change-visibility permission and the delete permission, because the item will delete itself. Removing them only needs the first. A team short link's expiry needs only the change-visibility permission: an expired link stops working but isn't deleted.

For a team item you see "Your role in (team name) can't (do that) - ask the team's owner or an admin". For team settings and similar actions you see "Only the team owner or admins can do that" (or "Only the team owner can do that"). People outside the team, and former members, get "Team not found" from the team's own screens and API, and a "not found" message for its items, such as "Upload not found", "Album not found", "Poll not found", "Board not found", "Link not found", "Drop not found" or "Template not found" (for example when they try to delete a team poll). Someone who only has a team poll's link can still open and answer it, but changing it gets "Only the organizer can change this poll".

Changing what members can do

The owner switches the member column on the Permissions tab. Under What members can do there is one switch for each setting that can change:

Each switch saves as soon as you flip it, one at a time, and shows "Saved" when it is done, with focus back on the switch. If the server refuses a change, the message is shown under the switches exactly as the server words it and the switch goes back. Under the switches the page notes that an expiry, delete after viewing or a drop's download limit needs both Change who can see items and their limits and Delete team items, and that opening and viewing items is always on, while team keys, removing members and the owner's own actions are never for members.

Turning Change who can see items and their limits off asks you first: "Stop members changing who can see team items? Every team board's invite link stops, and the team boards' display links and shared Discord preview templates' links get new addresses." Choose Turn off to go ahead.

Making an admin a member (the role menu on the Members tab) also asks first: "Make (name) a member? Every team board's invite link stops, and the team boards' display links and shared Discord preview templates' links get new addresses. They stop managing team boards and items." Choosing Admin for a member doesn't ask.

Removing a member asks "Remove (name) from (team)?". When you remove an admin, or a member while members may change who can see items, the question adds the same sentence about invite and display links, because those links are reset too. If the page can't tell whether members have that switch (it only shows it to the owner), a removal of a member says "If members can change who sees team items:" before it.

Website only

These can only be done while signed in on the website. An API key or team key gets "Sign in on the website to do this", even just to list the team's keys. A connected app can't use team actions at all.

• team settings and team keys
• removing members
• adding to a team, taking items out (including taking a calendar out) and deleting team items
• deleting or changing who sees the results of a team poll
• making a media board in a team and everything on a team board (a board is always changed from the website). Making a board with an API key or team key gets "Make boards on the website". On a team board, an API key or team key gets "Sign in on the website to do this" for its title, description and settings, deleting it, its invite link, removing people, its display link and its Discord picture
• making a short link or a drop in a team, changing a team link and deleting a team link or drop (an API key, team key or app token gets "Sign in on the website to do this" on a team link; reading its click stats works with a token)
• making a Discord preview template in a team, changing, sharing or deleting a team template, and opening one (an API key, team key or app token gets "Sign in on the website to do this" for the changes, and "Template not found" when it tries to open one)
• listing, making, changing, filling, reordering and deleting collections, personal or a team's (an API key, team key or app token gets "Sign in on the website to do this"; see Collections)
• the team's items list (GET /api/teams/:id/items)
• transferring the team and changing permissions
• replacing or restoring a file on a team item
• changing sharing and limits on a team item (who can see it, password, expiry, delete after viewing, team-only, link name)
• owner-only actions: deleting the team, billing, custom domain, promoting or demoting members

Making a meeting poll in a team with a key is the one exception to the wording: POST /api/meet with teamOwned: true and a teamId gets "Sign in to make a poll in a team" instead.

Storage

A team's items share one storage pool: 250 GB with the Teams plan (Copium staff can raise it for a team that asks, see Need more storage?) and 10 GB without. When the pool is full, new adds, uploads and larger replacements are refused with a message like "(team name) is out of storage space (9.8 GB of 10 GB) - an owner or admin can delete old team items". A replacement, or putting back a bigger earlier version, is refused if it would leave the pool over its limit. Leaving never moves anything onto your own storage. An item taken out of the team, or returned when the team is deleted, counts against its creator's storage again (see Taking items out of a team for when taking one out is refused).

The pool counts uploads (text files, pastes and transcripts sent with a team key included) and the pictures of the team's Discord preview templates. Drops have a pool of their own, separate from the storage pool and from anyone's personal drop limit. See Drops in a team.

Team videos. Videos a team owns are re-encoded in the background like any other upload (see Videos), and the re-encode counts against the team's storage pool, not the uploader's own space. A re-encode can make a file bigger (for example when HEVC, VP9 or AV1 video becomes H.264). If the bigger file would be over the uploader's video size limit (see Videos) or would push the pool over its limit, the re-encode is skipped: the video stays exactly as it was uploaded and keeps playing, and nothing is refused or marked failed. As with other uploads, a successful re-encode replaces the file and the original is not kept, so keep your own copy if you need it.

Teams without the Teams plan show how full the pools are to every member, under Storage on the Overview tab. Teams on the plan (paid or partner) don't see the Storage section for now. Their limits are unchanged and still apply, and a full pool is still refused with the message above. Uploads shows a bar and a line like "1.5 GB of 250 GB used" (or "5 MB used - no limit" when the pool has no limit). Drops shows a line like "3 of 50 drops, 1 GB of 20 GB". A line above them says the numbers are for the free tier. Once either pool is 90% full or more, a sentence warns that adding more will be refused when it is full.

Need more storage?

A team on the plan (paid or partner) can ask Copium staff for more storage. The Overview tab of such a team shows a Need more storage? section to the owner and admins. Members never see it, even ones the owner has given Team settings, and neither do teams without the plan. The section also shows "Your team's limit: (number) GB", the team's current storage limit. The request is only sent from the website, not with an API key.

• How much in total (GB) is optional: a whole number from 1 to 100000, the total you want for the team, not the extra.
• What do you need it for? is required: 20 to 2000 characters. A counter under the box shows how many you have used.
• Press Send request. A team has one request waiting at a time. While one is open, the form is replaced by "Request sent on (date). Staff will reply here." and anyone else who tries gets "There's already a request waiting for staff". You can send up to 3 requests a day. After that you see "You can send up to 3 storage requests a day - try again tomorrow". Requests that are refused (for example a message that is too short) don't count towards the 3. A team without a plan gets "Storage requests are for teams on a plan".
• When staff answer, the section says "Staff granted your request on (date)." or "Staff declined your request on (date).", with their note if they left one, and the form comes back so you can ask again.

If staff grant it, they usually set a storage limit for your team. It replaces the 250 GB while the plan is active (a partner plan or a paid one). The limit belongs to that plan: when the plan ends, or changes from a partner plan to a paid one or back, staff's limit is cleared. The team is then back to the 10 GB free size, and to the standard 250 GB if a plan starts again. Ask again if you still need more. Only Copium's owners and developers can grant storage, so a request answered by another staff member can only be declined. A limit can only be set while the team's plan is active; for a team without one, staff are told to start its plan first. A limit can also be set below what the team already uses; staff have to confirm that, and until the team is back under it nothing new can be added.

Your messages are kept with your account's data: they are in your data download and are deleted when you delete your account or the team is deleted.

Team keys

Team keys upload as the team, so what they upload is team-owned and counts against the team's pool. Its links use the site's address, or the team's custom domain while the team has the Teams plan, never the subdomain or domain of the member who made the key. Only the owner and admins can create them, never members, and creating one needs the Teams plan. A team can have up to 20 keys, and Sonoran CAD team connections count towards that limit. A key stops working when the member who made it leaves. See Apps and integrations for using them in FiveM and other tools.

Uploads sent as evidence with a team key stay under the evidence locker rules instead.

Text files, pastes and transcripts with a team key. A text file (.txt, a log or code), a paste sent with POST /api/paste and an HTML transcript sent with a team key belong to the team like any other team-key upload:

• They count against the team's storage pool. A transcript counts with the pictures copied for it, so its size is the page plus those pictures. When the pool is full they are refused with "(team name) is out of storage space (9.8 GB of 10 GB) - an owner or admin can delete old team items" and nothing is stored, including a transcript that fits but whose pictures don't.
• The key maker's own "delete my uploads after N days" setting doesn't apply to them. They only expire when someone allowed to change limits sets that.
• They show in the team library and the team's items list, and go with the team when a member leaves or deletes their account.
• With the team's "New shared uploads are team-only" switch on, they are for team members only, unless they are sent with public (in the JSON of POST /api/paste, or as a form field with a file).
• Sent through the game-server API, they are part of the team's server storage like files: listed by the team's keys, and deletable by them.
• A transcript's Discord role limits are changed by whoever the team lets change who can see an item (the website only), not by the key maker alone. This is checked again after Discord has been asked: if you were removed from the team meanwhile, nothing is changed and you get "Transcript not found" (or the usual role message if you lost the permission). If the transcript changed hands meanwhile, you get "This transcript changed while it was being checked - try again".
• While the team's evidence locker is on, text sent with a team key that asks to be locked as evidence (evidence set to a yes value such as 1, true, yes or on, in any case) stays as it always was: it isn't locked, isn't the team's and is the key maker's own upload. With the locker off, evidence changes nothing and the text belongs to the team.
• Pastes and transcripts you send as yourself (the website, a personal API key or token, ShareX) are yours and still follow your own expiry setting.

Links and drops with a team key. GET /api/links and GET /api/drops with a team key list the key maker's own links and drops and the ones that key's team owns, never another team's. Another team's link gets "Link not found" from its click stats. A personal API key still lists everything its maker can see.

Game-server keys. Of the files the team owns, a team key can delete only those that keys of the same team uploaded through the game-server API. Uploads from ShareX or another tool using a team key don't count, and everything else a team owns can only be deleted on the website. Older team-key uploads that aren't team-owned can still be deleted through the game-server API.

Albums in a team

Make an album in the team: in the team's library press New and choose Album, then press Create album on Albums. The note under Creating in (team name) says "(team name) will own this album. The team's owner decides who can rename, share or delete it." You can also add one of your own albums to a team with Add to team on its page. An older album you shared with a team (it shows Shared with (team name)) stays yours until you do, and it can only be added to that team. The Albums page no longer makes new albums of that older kind. The albums list and the album's page show Owned by (team name) for a team album, and Created by (name) on its page. Delete shows only when the team's roles let you delete it.

What you see in an album is decided for each upload and each viewer:

• People outside the team, and former members, see a locked tile for protected uploads (password, delete after viewing, or limited to certain Discord roles). Team-only uploads aren't shown to them at all.
• The album doesn't give direct file links for protected uploads; they open through their share page.
• A team album's invite link is shown only to members whose role lets them change who can see it (the owner and admins, and members if the owner allows it). A member who can only change the album doesn't see the link.
• The upload count on an album is counted for the person looking.

Meeting polls in a team

A meeting poll can belong to a team. Make it in the team (signed in: press New in the team's library and choose Poll, and Find a time to meet says Creating in (team name); signed-out visitors don't see that line), or add one of your own polls with Add to team (in the poll's Organizer section). You must be signed in on the website. Making a poll in a team sends teamOwned: true and the teamId to POST /api/meet. You can still make polls without a team. These are refused:

• not signed in: "Sign in to make a poll in a team"
• a teamId without teamOwned: true: "Send teamOwned: true to make it in a team"
• teamOwned: true without a team: "Pick the team that will own the poll"
• a team you aren't in: "Team not found"
• a role that can't add to the team: "Your role in (team name) can't add to the team - ask the team's owner or an admin"

The person who made it still gets the organizer link. On a team poll the team's roles decide who organizes it too. Anyone in the team who is allowed to change team items sees all answers, can change the poll and can remove other people's answers. Deleting a team poll needs the delete permission, and changing who sees the results needs the change-visibility permission. Both need the website.

The organizer link on a team poll can:

• change the title and description
• pick the final time, change the deadline, turn "if need be" on or off and close or reopen the poll

It can't, on its own:

• delete the poll
• change who sees the results
• remove someone else's answer

These get "Sign in on the website to do this". A member signed in on the website is checked against their role instead.

The organizer link stops working when the member who made the poll leaves the team or is removed, or deletes their account. Nobody gets a new one. It also stops working for as long as the member who made the poll can't change team items (the owner turned off the permission to change team items for members, the row in the roles table above) or their account is banned. While it is stopped, the link changes nothing and opens the poll like any visitor's view, so a poll that hides names shows none. It works again if the permission comes back or the ban is lifted. The poll stays with the team, and so do its answers. Team polls are still deleted 90 days after their last activity, like any other poll.

Short links in a team

A short link can belong to a team. Make it in the team (press New in the team's library and choose Short link; Links says Creating in (team name), for a single link or for Shorten many at once), or add one of your own links with Add to team (in the link's row on Links). You must be signed in on the website. Making a link in a team sends teamOwned: true and the teamId to POST /api/links (or POST /api/links/bulk). While you are creating in a team, the domain list leaves out your own subdomain and domains and a link can't be put on one, even after you search or reload the list. Open Links without a team and the domain you had chosen for your own links is selected again. You can still make links without a team. These are refused:

• a teamId without teamOwned: true: "Send teamOwned: true to make it in a team"
• teamOwned: true without a team: "Pick the team that will own the link"
• a team you aren't in: "Team not found"
• a role that can't add to the team: "Your role in (team name) can't add to the team - ask the team's owner or an admin"
• a key or app token: "Sign in on the website to do this"
• a domain that isn't one of the site's own: "Team links use the site's own domains - pick one of those"
• a password, expiry, click limit or start time on a new team link, for a role that can't change sharing: "Your role in (team name) can't change who can see it or its limits - ask the team's owner or an admin". A team link made without them is fine

Limits. The links you make count towards your own hourly limit whether they are yours or the team's. On top of that, the team's members together can make up to 300 links an hour: "(team name) can create up to 300 links an hour". Links added with Add to team count towards the same 300: once it is reached, adding one gives "(team name) can add up to 300 links an hour".

If the team is deleted, or you are removed from it or can no longer add to it, while a link is being made, the link isn't made ("Team not found", or the message for your role). Making several links at once (POST /api/links/bulk) stops there, and the rest aren't made.

What each role can do.

• Changing a link's title, where it goes and its preview card needs the permission to change team items. Copium+ rules still apply to the person making the change.
• Changing its expiry, click limit, password, start time, turning it on or off, and its domain needs the permission to change who can see an item.
• Deleting a team link needs the delete permission, on the website. A blocked link can't be deleted: "Blocked links are kept for review - contact Copium staff if you think this is a mistake".
• Everyone in the team can open its click stats. The detailed stats and CSV still need Copium+ for the person looking.
• The team's lists show where a link goes only to people who may change it. Everyone else sees the short link, its title, status and click count, and searching your Links page doesn't find a team link by where it goes unless you may change it. This isn't a secret: anyone can add + to a link without a password to see where it goes. A link with a password shows nothing of where it goes until the password is entered (see What people see when they open a link).
• A key, team key or app token can't change or delete a team link: you see "Sign in on the website to do this".
• Changing a team link's password signs out everyone who entered the old one.
• A change that is still being saved when the link is blocked, or when you are removed from the team, doesn't go through. A blocked link stays blocked: you see "This link was blocked by staff or the safety check and can’t be changed". If the link was taken out of the team or added to one meanwhile, you see "This link changed while you were saving - reload and try again".

Changing where it goes. Every change to a team link's destination or smart-link routes is recorded under the name of whoever changed it, and posted to the team's Discord activity feed (if it has one), including changes by the person who made the link. The message is "(name) changed where (short link) goes (now example.com)" for a new destination, and "(name) changed where (short link) goes (its device and country routes)" when only the routes changed. It shows the new website only, never the whole link. For a link with a password it doesn't name the website either: "(name) changed where (short link) goes". Discord shows no link preview under these posts.

Where it works. A team link works on the site's own domains and on a custom domain shared with the team, while the team has the Teams plan. It doesn't work on a member's own subdomain or domain, not even its creator's: there it shows "Link not found", and its password form answers the same as for a link that doesn't exist.

Preview card picture. A team link's card picture must be a public upload the team owns: "Pick the card image from the team's uploads (paste its link)". A private upload can't be used.

Other things to know.

• POST /api/shorten with a team key makes a link for the person who made the key, not for the team.
• A team link keeps working when the member who made it leaves the team or deletes their account. It stops if that member is banned, and so does its password form.
• A team link is left out of its maker's own link totals, stats, weekly recap, spreadsheet export, link-in-bio and /copium search. It still shows in their Links page while they are in the team.
• A blocked link can't be added to a team, and a team delete never deletes one. It stays with Copium staff for review.

Drops in a team

Copium Drop (a Copium+ feature that sends a file as a download link that expires) has no page of its own yet. These are the rules for a team's drops.

A drop can belong to a team. Send it in the team (press New in the team's library and choose Drop; Copium Drop says Creating in (team name) before Send), or add one of your own drops with Add to team (in the drop's row under Your drops). You must be signed in on the website, and the person sending needs Copium+ ("Copium Drop is a Copium+ feature"). Sending to a team adds the form fields teamOwned=true and teamId to POST /api/drops. These are refused:

• without Copium+: "Copium Drop is a Copium+ feature"
• with an API key, team key or app token: "Send drops from the website"
• a teamId without teamOwned=true: "Send teamOwned: true to make it in a team"
• teamOwned=true without a team: "Pick the team that will own the drop"
• a team you aren't in: "Team not found"
• a role that can't add to the team: "Your role in (team name) can't add to the team - ask the team's owner or an admin"

The team's drop pool. With the Teams plan a team can have up to 50 drops at once, and they can total up to 20 GB. Without the plan it is up to 10 drops and 2 GB. This pool is separate from the team's storage pool and from the drops each member sends for themselves. You see:

• "(team name) can have up to 50 drops at once - delete some first" (10 without the Teams plan)
• "(team name)'s drops can total up to 20 GB at once - delete some first" (2 GB without the Teams plan)

Limits. A password is allowed. A download limit makes the drop remove itself, so it needs both the permission to change who can see an item and the delete permission. Without the first you see "Your role in (team name) can't change who can see it or its limits - ask the team's owner or an admin", and without the second "Your role in (team name) can't delete it - ask the team's owner or an admin". A drop with a download limit can't be added to a team afterwards.

Expiry. Team drops still expire like every other drop (after at most 30 days). Expired drops don't count towards the pool.

Deleting. Deleting a team drop needs the delete permission and the website. A key, team key or app token gets "Sign in on the website to do this", and a team key gets "Drop not found" for another team's drop. Its file is removed from storage once the delete has gone through. Copium staff can still take a drop down, and a drop that people report is removed as before. A drop that is already gone can't be deleted again. Deleting it from the team's items gives "This drop is already gone - only its record is left", and DELETE /api/drops/:id gives "Drop not found".

Other things to know.

• The drop's page, its password form and its download link follow the member who sent it: if that member is banned, they stop working. The same goes for a member's own drops.
• The drop's page says it is from the team (the team's name), not who sent it.
• GET /api/drops with a team key lists only your own drops and that team's (see Team keys).
• A team drop stays, with its file, when the member who sent it leaves or deletes their account.
• A team drop doesn't count against the sender's own limit of 50 drops and 20 GB. It does again if it is returned to them, so it can only be taken out of the team while it fits in that limit: otherwise you see "That would put its creator over their own drop limit - delete it instead". When the team is deleted, a drop that doesn't fit is deleted instead of returned.

Discord preview templates in a team

A saved template of the Discord profile & server preview can belong to a team. Save it in the team (press New in the team's library and choose Discord preview template; the saved templates say Creating in (team name) below Template name; press Save as new), or add one of your own templates with Add to team (in your saved templates list). You must be signed in on the website. Saving a template in a team sends teamOwned: true and the teamId to POST /api/discord-preview/templates. Loading a team's template doesn't change a Creating in line: with one, Save as new saves to that team. With none, it saves to the loaded template's team (the page then says Creating in (team name) above the buttons) while you may still add to that team, and otherwise to your own templates. If the address names a team you can't add to (the page says what you make there is yours), Save as new stays in your own templates, even with a team template loaded. Editing a loaded team template with Save changes keeps its team. You can still save templates without a team. These are refused:

• a teamId without teamOwned: true: "Send teamOwned: true to make it in a team"
• teamOwned: true without a team: "Pick the team that will own the template"
• a team you aren't in: "Team not found"
• a role that can't add to the team: "Your role in (team name) can't add to the team - ask the team's owner or an admin"
• an API key, team key or app token: "Sign in on the website to do this"
• a team that already has 50 templates: "(team name) can keep up to 50 templates - delete one first"

A team can keep up to 50 templates, whatever its members' own limits are (5, or 50 with Copium+). Your own limit counts only the templates you keep for yourself. On the website, your list of saved templates also shows the team templates you made, for as long as you're in that team. The team's other templates are in the team's items list.

Who can do what.

• Opening a team template is for everyone in the team. Changing its name, settings and pictures needs the permission to change team items.
• Sharing it needs the permission to change who can see an item, and the person sharing needs Copium+ ("This is a Copium+ feature"); the Teams plan gives every member that. Taking the share link down needs the same permission, and works without Copium+.
• Deleting it needs the delete permission. Taking it out of the team needs the take-out permission.
• The person who made it gets nothing extra. Once they leave the team, they get "Template not found".

Pictures. The pictures of a team template belong to the team.

• A picture you upload for a team template becomes the team's when you save the template, and counts against the team's storage pool. A full pool refuses the save with the usual "(team name) is out of storage space" message.
• A team template can use pictures the team owns and pictures you upload for it. While a team template is loaded, or you are creating in a team with nothing loaded, the picture buttons read Pick from the team and list only the team's own public uploads (once a template is loaded, that means the loaded template's team, even if the address names another team; Save as new into a different team than the loaded template's refuses the pictures already stored for it, see below): no pictures of yours, no PNGs (upload a PNG straight into the slot), and none that is protected: with a password, delete after viewing, an expiry that has passed, or team-only. (A picture with an expiry still ahead is listed.) On a page without a team, with no team template loaded, the buttons say Pick from my Copium and list your own library, so a new personal template never offers the team's pictures. The window says "On a team template, pick a picture the team owns or upload one for it". A picture from your own library is refused if it is sent anyway, and the slot shows Copium's reason: "On a team template, pick a picture the team owns or upload one for it".
• Pictures already stored for the loaded template can't move to another team. With Save as new into a different team, the page says "Pictures from the loaded template can't move to (team name); upload them again.", and the save is refused for those pictures: the slot says "This picture can't be used in a template. It may be private or protected. Pick another, or upload it into the slot." Upload the picture again into the slot for the new team.
• A picture one of your other templates also uses is refused the same way (the slot says "This picture can't be used in a template. It may be private or protected. Pick another, or upload it into the slot."); upload it again for this template.
• When you add a template to a team, the pictures you uploaded only for that template become the team's too. A picture from your library, or one another of your templates uses, stays yours. The team template keeps showing it while it exists and you're in the team. Once you leave or are removed, the team sees it as missing and the share page leaves it out. Nothing is deleted, and it shows again if you rejoin.
• A template's pictures never show in the team library or its counts, and they can't be renamed or deleted on their own: they are deleted with the template, or when they are replaced on it. A picture that is still yours is not deleted at once by someone else's change to the team template: it just stops being used there. Once no template of yours or the team's uses it and it is more than a day old, the hourly clean-up of unused template pictures removes it, as with any picture uploaded for templates.
• A picture two of the team's templates show stays with the team when one of them is deleted or taken out.

The share link. A shared template has a public page that anyone with the link can open. It is a secret, so only people who may change sharing see it; the others see that the template is shared.

• Adding a template to a team stops its old link. If it was shared, it gets a new link. Taking it out of the team, or the team being deleted, leaves it without a link.
• The link changes when someone who could see it leaves the team, is removed, is demoted from admin, is banned or deletes their account, and when the owner stops letting members change who can see an item. A member who couldn't see it leaving changes nothing.
• The page is looked at again every time it is opened. It works while the team still owns the template, the member who made it isn't banned, and the team has a plan or that member has Copium+ while still on the team. Once that member has left the team or deleted their account, only the team's plan counts. Otherwise it shows "This preview is not being shared right now". It works again when the ban is lifted or that member rejoins the team.
• A report about the page's text, or staff taking the page down, is noted in the moderation history of the member who made the template with the team and the template named, never the link.

What it shows. A preview is a mock-up: the name, username, pronouns, bio and pictures typed or chosen in the template. Nothing is filled in from the account of the member who made it. The public page, the team's list and the template itself show nothing of their Discord profile, picture or email beyond what they put in it. The team's list shows their name as "created by", as for every team item, and "Deleted member" after they delete their account.

Taking it out, or deleting the team. The template goes back to its creator without its share link. Their own pictures come back to them. When you take it out, a picture of theirs that another team template also shows stays with the team instead, and the template taken out stops using it. A picture another member added is no longer used by it either. A picture uploaded for templates that no template uses is removed by a clean-up that runs every hour, once it was uploaded more than a day ago, so an older one can go within the hour. Taking it out is refused when it would put its creator over their own template limit: "That would put its creator over their own template limit - delete it instead". On a site that limits each member's storage, it is also refused when the pictures coming back would put them over it: "That would put its creator over their own storage space - delete it instead". Deleting the team still hands it back, whatever their limits, unless the creator's account is gone or banned: then the template is deleted with the pictures the team owns. When the team is deleted, a picture two of its templates share goes back to the member who uploaded it, and stays on their template when that goes back to them too. Another member's template stops using it. A picture held for review is never deleted, and one locked as evidence is never touched.

Deleting it. Deleting a team template deletes the pictures only it used, and leaves a record in the team's history. A team template stays when the member who made it leaves the team or deletes their account, with its pictures.

Media boards in a team

A media board can belong to a team. Make it in the team (press New in the team's library and choose Board; the page says Creating in (team name) next to New board), or add one of your own boards with Add to team (in the board's Share panel). You must be signed in on the website: an API key or team key gets "Make boards on the website". Making a board in a team sends teamOwned: true and the teamId to POST /api/boards. You can still make boards without a team. These are refused:

• a teamId without teamOwned: true: "Send teamOwned: true to make it in a team"
• teamOwned: true without a team: "Pick the team that will own the board"
• a team you aren't in: "Team not found"
• a role that can't add to the team: "Your role in (team name) can't add to the team - ask the team's owner or an admin"
• a team that already has 200 boards: "(team name) can have up to 200 boards"

A board made in a team is for the team only (not open to anyone with its link) and has no invite link until someone who may change sharing makes one. The 30 boards you can own count only the boards you own on your own, and the team's 200 count only the team's.

Who can do what.

• The team's owner and admins are the board's owner: they can change everything on it, remove anyone's things, lock it and delete it.
• A member whose role lets them change team items is a board member: they can add things, comment, and move, change and remove their own things, and change the board's title and description. While the board is locked only its owner can change it, its title and description included: members get "The owner locked this board". On a team board the lock setting in the Share panel reads "Lock it - only the team's owner and admins can change things".
• Pins and replies follow the permission to comment too. If the owner switches it off for members, a member can still change the board but gets "Your role in (team name) can't comment on it - ask the team's owner or an admin" when they add a pin or reply, or change or resolve one.
• You can always delete your own pins and replies, whatever your role, as long as you can still open the board: also while you can only look or comments are switched off. Deleting someone else's needs the board's owner.
• A member who can't change team items only looks, and can't comment either, even while the permission to comment is on. They get "Your role in (team name) can't change it - ask the team's owner or an admin". On the open board they aren't shown to the others, and they aren't shown who else has it open. A display page of a team board isn't shown who has it open either.
• On a team board that isn't open to anyone with its link, the display page and image link don't show who added what, who made the board or its people. On a board that is open to anyone with its link, they show them as the board itself does.
• Changing whether the board is team-only or open to anyone with its link, locking it, the invite link, removing a guest, the display link and the Discord picture needs the permission to change who can see an item. Without it you see "Your role in (team name) can't change who can see it or its limits - ask the team's owner or an admin". Members without it aren't shown the invite or display link.
• Deleting a team board needs the delete permission: "Your role in (team name) can't delete it - ask the team's owner or an admin".
• The person who made it gets nothing extra. The board's People list shows them as "made it", never as its owner, and no longer lists them once they leave the team. Once they leave they get "Board not found", like anyone outside the team, unless the board is open to anyone with its link: then they can look, as anyone can, and nothing more.
• Someone outside the team who joined the board with an invite link (one made by someone who may change sharing, or one from before the board was added to the team) is a guest. A guest never does more than the team's members: while members may change team items a guest can add things and change their own, and otherwise only looks and gets "You can only look at this board for now". While members may not comment, a guest gets "Comments are off for you on this board".
• For a team member, their role in the team always decides what they can do, whatever an invite link once gave them. If a team member also joined by an invite link, that place ends when they leave the team.

Open boards update at once. A board that is open on screen is checked again whenever the team changes who may be there: someone who joins, leaves or is removed, a role or permission change, a ban, an account being deleted, a board taken out of the team and a deleted team. Someone who no longer has access is closed out of the open board straight away. A member who can now only look stays on it but is no longer shown to the others, and is no longer shown who else is there. When what you can do on an open board changes, the board reloads to show it. A member who is removed from the team while saving a change doesn't get the change saved. Even if nothing tells the board, someone moving around on it is checked again at least once a second.

Pictures. Besides your own uploads, anyone in the team who may add to a team board can put uploads the team owns on it: the team's owner and admins, and members whose role lets them change team items (while the board isn't locked). A guest from outside the team can't. The uploads must be public (no password, delete after viewing, team-only setting or limit to certain Discord roles). Another team's uploads and other members' personal uploads can't be added: "None of those can go on a board - only your own uploads (or the team's) that anyone can view". A picture the team owns is shown with the team's links: the site, or the custom domain shared with the team while the team has the Teams plan. The board's own page is on the site.

An upload the team owns is only shown on the team's own boards. On any other board it is missing, as if it had been deleted: on the board, its display page, its picture and its Discord picture. That goes for a personal board that had one of your uploads on it before you added that upload to a team: if the upload goes back to you (taken out of the team, or the team is deleted), it shows there again. Open boards and display pages catch up straight away. An image link stops showing it straight away, and shows it again when it is next redrawn (at most once a minute).

A board that leaves the team (taken out, or handed back when the team is deleted) loses the team's uploads for good. They are removed from it, with any arrows attached to them, and undo can't bring them back, even once those uploads go back to whoever uploaded them. Everyone's own uploads and everything else on the board stay.

Display link, Discord picture and invite link. On a team board these work for as long as the team owns the board and the member who made it isn't banned. While that member is banned they stop, and they work again if the ban is lifted. A link that stops this way is just a link that doesn't work: whoever has access to the board in the team still sees it as usual. An invite link that stops gives "That invite link doesn't work any more - ask for a new one".

• Add to team The old invite link stops (people who already joined stay) and the board becomes team-only. If it had a display link, the display link gets a new address: the old one stops working and display pages open with it are closed. Its Discord picture stops, and its webhook is removed. Someone who may change sharing can open the board to anyone with its link again, turn the display link or Discord picture back on, or make a new invite link.
• Taken out of the team, or handed back when the team is deleted. The board goes back to its creator without its display link, Discord picture or invite link, and without the team's uploads: the links stop working, and a Discord picture that was about to be updated isn't sent. The creator can turn the links on again.
• Invite links are reset. Every invite link of the team's boards stops when someone leaves the team, is removed or deletes their account, when an admin is made a member, and when the owner stops letting members change who can see an item. People who joined stay. Whoever may change sharing can make a new one.
• Display links get a new address. Every display link of the team's boards gets a new address when someone who could see them leaves the team, is removed, is banned or deletes their account (the owner, an admin, or a member while members may change who can see an item), when an admin is made a member, and when the owner stops letting members change who can see an item. The old address, and its image link, stop working at once, and display pages open with it are closed. A member who couldn't see the display links leaving changes nothing. Whoever may change sharing finds the new address in the board's Share panel.

Other things to know.

• A team board stays, with its things, comments and people, when the member who made it leaves the team or deletes their account. The notes and comments that member left on it stay too, shown as "Deleted member".
• A team board isn't counted in its maker's 30 boards, and the list of your own boards (GET /api/boards) shows the ones you made in a team while you are in it, marked teamOwned. The team's other boards are in the team's items list.
• Taking a board out of a team is refused when its maker already owns 30 boards of their own: "That would put its creator over their own board limit - delete it instead". Deleting the team still hands it back, even over that limit.
• Copium staff can look in, and remove things for moderation, as on any board.

Calendars shown in a team

A synced Google Calendar (see the Discord bot) can be shown in a team. Showing a calendar doesn't hand it over:

• Only the member whose Google connection it uses can show it, and only while signed in on the website. On Google Calendar for Discord, press Show in team on the calendar's card, or add a new calendar from the team library's New menu (Calendar), where the Add a calendar form says Showing in (team name) (there is no box to tick there either). If you connect a Google account first, the page comes back without the team: choose Calendar from the team library's New menu again. The card then says Shown in (team name) and has Stop showing.
• It stays with that member. Editing, syncing and deleting it stay with the people who manage the Discord server. A team role never gives access to a Discord server.
• The team's list shows the calendar's name, the server's name and icon, when it last synced, whether it has a problem and how many events are coming up. Channels, roles, the Google account and the calendar ID are not shown. Google names a main calendar after its account's email address, so when the name is an email address, or the same as the calendar ID or the Google account's email, the team sees "Calendar" instead, and searching the list can't find it by that name.
• A calendar is shown in one team at a time. GET /api/calendar tells you which team shows each of your own syncs in teamId (empty when none).
• The member who showed it, or the team's owner or admins, can take it out, on the website only: with an API key, team key or token you see "Sign in on the website to do this" and the calendar stays shown. Taking it out leaves the calendar as it was.
• Creating a calendar sync with teamOwned: true is refused: "Calendars can't belong to a team - they can only be shown in one". Send a teamId instead to show a new calendar in a team you can add to.

The team's items list

The team library page uses this list (its Uploads tab uses GET /api/teams/:id/library). GET /api/teams/:id/items lists the items of one kind that the team holds, newest first, 60 to a page. It works only while signed in on the website: an API key, team key or connected app can't use it. Everyone in the team can open it. Copium staff can look but not change anything, and each visit is logged.

The answer has type, items, nextCursor and, on the first page, counts with the number of items of each kind. Each item has id, title, url, teamOwned, createdBy, addedBy, addedAt and can (what you may do with it: edit, share, remove, delete) plus the details of its kind. A link lists its code, short address, title, status, limits flags and clicks, and where it goes only for people who may change it. A drop lists its name, size, expiry, downloads and page address, never its download link. A board lists its title, how many things are on it, up to four public pictures as a cover, whether it is team-only and locked, and when it changed, never its invite link, display link or Discord webhook. A Discord preview template (dp_template) lists its name, whether it is shared, when it changed and, only for people who may change sharing, its share link, never its settings or pictures. Only drops that can still be downloaded are listed and counted: not removed, expired or used up. A collection (collection) lists its title, description, how many things it holds (items) and when it changed, never what is in it. See Collections. Uploads that are Discord preview template pictures aren't part of the team library or its counts.

What the lists tell the website about team items

Besides the items list, a few answers carry extra fields so the website can show only what you may do. They are for the website: the server still checks every request.

• GET /api/teams/:id/storage-request gives the team's latest storage request as request (status of open, granted or declined, requestedGb, createdAt, staffNote, resolvedAt), or request: null, plus quotaGb, the team's current limit in GB (rounded; usage isn't included). POST /api/teams/:id/storage-request with message (20 to 2000 characters) and an optional whole gb from 1 to 100000 sends one and returns 201. Both work only while signed in on the website, for the owner and admins. GET works for them even without a plan, while POST only works for a team on a plan ("Storage requests are for teams on a plan" otherwise). Non-members get "Team not found".
• GET /api/teams gives each team a storage with used and quota for its storage pool (quota is the team's own limit when staff have set one and its plan is active) and, inside it, drops for its drop pool: count (drops that can still be downloaded), max, used (their total size in bytes) and quota. A max or quota of 0 means no limit.
• GET /api/teams/:id/library also gives counts, the number of items of each kind, on its first page (the same numbers as the items list).
• In your own lists (GET /api/images, GET /api/links, GET /api/drops and GET /api/me/meets), a row the team owns has can, the same answers as in the items list: edit, share, remove and delete (a poll has edit, share and delete). remove is false for locked evidence and when the item could not go back to its maker (their account is gone or banned, or it would put them over their own limit), as in the items list. Rows that are only yours have no can.
• A meeting poll (GET /api/meet/:id) has yours, which is true when you are signed in and made this poll for yourself, not for a team. A poll a team owns, when you are signed in as a member of that team, also has team (id and name) and can (edit, share and delete; share is true only if edit is too, because changing who sees the results needs the organizer). Anyone else, and anyone using only an organizer link, a key or a token, gets neither.

Leaving a team

When you leave or are removed, team-owned items stay with the team. Uploads you only shared to the team library are taken out of it, and albums you shared stay shared until you take them out. Your team keys stop working. If you had shared your custom domain with the team, it is unshared. Team uploads and albums you made stop opening on your own subdomain or domain (their links on the site keep working).

Team short links and drops you made stay with the team, and you can no longer see or change them. Team Discord preview templates you made stay with the team, with their pictures, and you get "Template not found" for them. If you could see their share links, those get new links, so the ones you kept stop working. Team polls you made stay with the team, and your organizer link for them stops working. Team boards you made stay with the team and you get "Board not found" for them (unless a board is open to anyone with its link, where you can only look). If you had joined a team board with an invite link too, that place ends. A team board you have open is closed at once, unless it is open to anyone with its link: then it stays open, and you can only look and aren't shown to the others. Every invite link of the team's boards stops working when anyone leaves or is removed, so nobody can come back in with one they kept. If you could see the boards' display links (as the owner or an admin, or as a member while members may change who can see an item), they all get a new address too, so the ones you kept stop working. Calendars you showed in the team stop being shown, because their Google connection leaves with you. Collections the team owns stay with the team, with the things you added to them, and still show you as Created by. Your own collections lose anything you could only open through the team, for good: it does not come back if you rejoin. Other members' own collections lose the uploads you shared with the team at the next hourly clean-up, once they are no longer shared with it (albums you shared stay shared, so they stay). Something only held, quarantined or protected for a while (a password, burn-after-viewing or an expiry) is never removed by the clean-up: it keeps its entry and shows as unavailable until it is back.

Once a team owns something

When an upload becomes team-owned:

• It comes off your profile, folders and tags.
• Bulk tools skip it.
• It's left out of your stats and weekly recap.
• /copium share and Discord search don't offer it.
• It can't be used on your own boards (the team's members can put it on the team's boards, see Media boards in a team), as the preview card image on your own short links, a watermark logo, a picture on one of your own Discord preview templates or a profile banner. It can be a picture on the team's own Discord preview templates (see Discord preview templates in a team) and the card image on the team's short links (see Short links in a team).
• It stops counting against your own storage and counts against the team pool.
• It still shows in My uploads while you're in the team.
• Its links use the site's address, or the custom domain shared with the team while the team has the Teams plan, never your own subdomain or domain. This goes for team albums and for what a team key uploads too. Older links to it on your own subdomain or domain keep working while you're in the team, and stop when you leave or are removed. Other members' own subdomains and domains never show it.

Taking items out of a team

A taken-out item goes back to whoever made it. If they can't take it back, you see "The person who made it can't take it back - delete it instead". It also has to fit within their own limits:

• a drop that would put them over their own drop limit (50 drops and 20 GB): "That would put its creator over their own drop limit - delete it instead"
• on a site that limits each member's storage, an upload that would put them over it: "That would put its creator over their own storage space - delete it instead"
• a board, when they already own 30 boards of their own: "That would put its creator over their own board limit - delete it instead"
• a Discord preview template, when they already keep as many of their own as they are allowed (5, or 50 with Copium+): "That would put its creator over their own template limit - delete it instead"
• on a site that limits each member's storage, a Discord preview template whose pictures coming back to them would put them over it: "That would put its creator over their own storage space - delete it instead"
• a collection, when they already keep as many of their own as they are allowed (10, or 200 with Copium+): "That would put its creator over their own collection limit - delete it instead", or when it holds more things than their own collections can (100, or 500 with Copium+): "It has more items than its creator's own collections can hold - remove some first"

A thing taken out of a team also leaves the team's collections straight away. It leaves other members' own collections at the next hourly clean-up (until then it shows as unavailable to those who can change the collection). See Collections.

Deleting the team still returns uploads whatever their creator's storage, and boards, Discord preview templates and collections whatever their creator's limits (see Delete a team).

Transfer ownership

The owner can hand the team to one of its admins, and becomes an admin. Make the person an admin first (the role menu on the Members tab). Then press Transfer ownership under the team's tabs, pick the new owner (the list shows the team's admins), and press Transfer ownership again. With no admins the dialog says "Make someone an admin first, then hand the team over." and has nothing to pick.

Cancel has focus when the dialog opens, and if the server refuses, focus moves to its message. Before you press it, the dialog lists what applies: the plan notice below (with Manage billing while a paid plan still renews), a note if the team holds locked evidence, a note about the team's shared domain (if the domain is yours, it stays shared with the team while you are a member, and stops if you leave or delete your account; if another member shared it, it stops being shared if they leave or delete their account; either way the new owner can unshare it), and "You'll become an admin." These are hints. The button always works, and if the server refuses, its message appears in the dialog exactly as written. When it works, you see "(name) now owns (team)".

The transfer is refused:

• while the team holds locked evidence: "This team holds locked evidence - release it before handing the team over"
• while a paid Teams plan isn't set to cancel at the period end: "Cancel the Teams plan subscription first (Manage billing). The team keeps the plan until it ends."
• if the new owner is banned or can't take over: "They can't take over the team"
• if they already own the most teams allowed (3): "They already own the most teams they can"

Any open checkout of the old owner expires. The new owner subscribes with their own card. When the plan is already set to cancel at the period end, the dialog says "The plan runs to the end of its paid period. The new owner subscribes with their own card."

Delete a team

Only the owner can, with Delete team under the team's tabs. The dialog first shows what will happen to each kind of item, counted by the server: a table with a row for each kind that has anything (Uploads, Albums, Boards, Polls, Links, Drops, Discord previews, Calendars, Collections) and three columns, Go back to whoever made them, Deleted for good and Kept for review. Calendars show as "stop being shown" and are never deleted. Collections follow their own row in the table (they go back to whoever made them, or are deleted for good when that account is gone or banned), and the things in them are kept: deleting a collection never deletes what it points to. If anything would be deleted for good, you must tick "I understand (number) items will be deleted for good" before Delete team works; pressing it first moves you to the box and says "Tick the box to confirm". If the table can't load, the dialog shows the reason with Try again, and asks you to tick "I understand some items may be deleted for good". Cancel has focus when the dialog opens, and pressing Try again clears the box. If the server refuses, focus moves to its message. The dialog also repeats the evidence and plan notices below, and shows the server's message in the dialog if it refuses.

A team that has no live paid plan and no locked evidence can be deleted. Otherwise you see one of:

• while the team holds locked evidence: "This team holds locked evidence - export it and release it before deleting the team"
• while the plan is set to cancel: "The Teams plan ends on (date) - you can delete the team after that"
• while the plan isn't set to cancel: "Cancel the Teams plan subscription first (Manage billing)"

Deleting removes the members. Team comments are deleted. Each team-owned item (uploads, albums, boards, polls, short links, drops, Discord preview templates and collections) goes back to its creator, or is deleted if the creator's account is gone or banned and can't take it back. A poll that is deleted goes with its answers. A board that is deleted goes with its things, comments and people (the uploads on it stay with their owners); one that comes back keeps all of them but not its display link, Discord picture or invite link, nor the team's uploads on it (see Media boards in a team), and anyone else from the team who has it open is closed out (or, on a board open to anyone with its link, can only look). A drop that is deleted has its file removed once the delete has gone through, and a drop that comes back keeps its file. A drop only comes back while it fits in its creator's own drop limit (50 drops and 20 GB, counting the others coming back to them): one that doesn't is deleted. A Discord preview template that comes back brings the pictures only it used and loses its share link; one that is deleted is deleted with the pictures the team owns for it, except pictures held for review, which are never deleted. A collection comes back with its list of things, without a public link, even over its creator's limits; the things in it are not touched, and one whose creator's account is gone is deleted. Once the team is gone, each of its former members' own collections (the ones that just came back included) lose anything they could only open through the team. Uploads always come back, even over their creator's storage. The summary shown before you delete counts these the same way. A blocked link is never deleted: it is released to its creator. The record of a drop that is already gone (removed, expired or used up) is released too, and is counted as held, not returned. Albums people only shared with the team stay with their owners. Calendars shown in the team stop being shown and are otherwise left alone. Items held for review, a takedown or retention are kept and released, not deleted. The team's invite stops, shared domains are unshared and team keys are removed.

When an owner deletes their account

See Delete your account for what you see. For each team you own:

• The team passes to the admin (or, if there's none, the member) who has been in the team longest. Banned or deleted accounts are skipped. A paid Teams plan then ends at the end of the period already paid for, and the old payment details are detached. The new owner can subscribe with their own card.
• A team nobody else can take over (banned or deleted members are skipped) is deleted, its invite stops and its plan is cancelled straight away.
• A team that holds locked evidence and has nobody to hand it to is kept frozen for Copium staff, and its paid plan ends at the end of the paid period.

Team-owned items stay with the team and show as created by "Deleted member". A team Discord preview template made by the member stays, with its pictures, and its share page keeps working while the team has a plan; their own templates are deleted with their pictures. A team poll made by the member who deleted their account keeps its answers, and its organizer link stops working. Their personal polls are deleted, and calendar syncs they made are removed as before. A team's short links and drops made by the member also stay, and a drop keeps its file. A team's media boards made by the member stay too, with the notes and comments the member left on them. A team's collections made by the member stay as well, with the things the member added to them, and their own collections are deleted (the things in them are not touched). Albums the member shared with a team the older way stop being shared with it, and so do uploads of theirs kept because they are held for review (one restored later is not shown to the team): they leave the team's library, are no longer shown in collections, and their entries go at the next hourly clean-up. The team's board links are dealt with as when someone leaves: every invite link of the team's boards stops, and the display links get a new address if the member could see them; the member's own boards, and their notes and comments on other people's boards, are deleted. Their own short links (except blocked ones) and drops are deleted as before.

Billing notes

If a Teams subscription is for a team that was deleted, was started by a former owner, or renewed after the team changed hands, Copium cancels it and staff refund what it charged. A subscription is cancelled for a team only if this server deleted that team. For an unknown team, staff are alerted instead.

Deleting a team item

On the team library page these messages come from Delete for good, not from the upload page. Deleting can be refused with:

• "This is still being processed - try again in a minute"
• "This is held for review or legal reasons and can't be deleted"
• for a blocked link: "Blocked links are kept for review - contact Copium staff if you think this is a mistake"
• for a drop that is already gone: "This drop is already gone - only its record is left"

Your data

Your data export lists team-owned items, short links and Discord preview templates included, as metadata only (id, date and team), without files, titles, names, settings or destinations. Moderation entries about a team's link, drop or board (such as a report or a takedown of one you made, a change you made to where a team link goes, or staff looking in at or removing things from a team board) stay in your moderation history with the team named, but without the link's destinations, why it was blocked, the drop's file name or the board's title. A report or a staff takedown of a team Discord preview template's share page names the team and the template, never the share link. The Teams wording in the Privacy Policy and Terms covers who can see what and who is responsible for what.