How to share same table across teammates?
", "messages": [ { "id": "3312526", "postDate": "11/07/2025 11:36:14", "content": "How to share same table across teammates?
", "rawMarkdown": "How to share same table across teammates?", "votes": null }, { "id": "3319025", "postDate": "11/11/2025 14:22:06", "content": "3LC projects (including Tables and Runs) are designed to be shareable. There are multiple ways to share 3LC projects.
\nFor all these options to share, one thing that is needed to be taken care of is aliases. For example, if all the images are written and stored in absolute paths when creating 3LC Tables, you can imagine the images won't be able to loaded when they open the same Tables from their machine. To learn more about aliases, please refer to this Doc at https://docs.3lc.ai/3lc/latest/user-guide/sharing.html.
", "rawMarkdown": "3LC projects (including Tables and Runs) are designed to be shareable. There are multiple ways to share 3LC projects.\n\n- If your project is located in a common place (e.g., aws s3) that you and your teammates can access, anyone of your team can put the project's URL under \"project-scan-urls\" in the config.yaml file. To learn where to find the config file at https://docs.3lc.ai/3lc/latest/user-guide/file-locations.html \n- You can send the 3LC project to your teammates. Also use the link above to find where your project is. \n- You can also just share/send a data revision Table to your teammates. A data revision Table is located at \"[project name]/datasets/[dataset name]/tables/[table name]\". For this to work, the prior revisions on this dataset has to be the same across the users, because a child revision Table is dependent on its parent revision Table. \n\nFor all these options to share, one thing that is needed to be taken care of is aliases. For example, if all the images are written and stored in absolute paths when creating 3LC Tables, you can imagine the images won't be able to loaded when they open the same Tables from their machine. To learn more about aliases, please refer to this Doc at https://docs.3lc.ai/3lc/latest/user-guide/sharing.html.", "votes": null }, { "id": "3319047", "postDate": "11/11/2025 14:30:57", "content": "One more thing about collaboration: If multiple people work on editing the data and committing revisions, the best practice is to work on it in sequence rather than simultaneously. This is because of the same reason stated above - a child revision is dependent on its parent revision. All the revisions should be in the same lineage tree. For example, 1st person made some edits and committed a revision R1, then the 2nd person opens the revision R1 and work on it to make revision R2. In a training Run, you can also select which revision Table to display in that Run, which will allow you to work on editing any revision on a training Run. Please refer this How-to page for more https://docs.3lc.ai/3lc/latest/how-to/basics/run-details.html.
", "rawMarkdown": "One more thing about collaboration: If multiple people work on editing the data and committing revisions, the best practice is to work on it in sequence rather than simultaneously. This is because of the same reason stated above - a child revision is dependent on its parent revision. All the revisions should be in the same lineage tree. For example, 1st person made some edits and committed a revision R1, then the 2nd person opens the revision R1 and work on it to make revision R2. In a training Run, you can also select which revision Table to display in that Run, which will allow you to work on editing any revision on a training Run. Please refer this How-to page for more https://docs.3lc.ai/3lc/latest/how-to/basics/run-details.html.", "votes": null } ], "comments": [ { "id": 3319025, "author_name": "dianhebluware", "author_url": "", "post_date": "11/11/2025 14:22:06", "content": "3LC projects (including Tables and Runs) are designed to be shareable. There are multiple ways to share 3LC projects.
\nFor all these options to share, one thing that is needed to be taken care of is aliases. For example, if all the images are written and stored in absolute paths when creating 3LC Tables, you can imagine the images won't be able to loaded when they open the same Tables from their machine. To learn more about aliases, please refer to this Doc at https://docs.3lc.ai/3lc/latest/user-guide/sharing.html.
", "votes": null, "replies": [ { "id": 3319047, "author_name": "dianhebluware", "author_url": "", "post_date": "11/11/2025 14:30:57", "content": "One more thing about collaboration: If multiple people work on editing the data and committing revisions, the best practice is to work on it in sequence rather than simultaneously. This is because of the same reason stated above - a child revision is dependent on its parent revision. All the revisions should be in the same lineage tree. For example, 1st person made some edits and committed a revision R1, then the 2nd person opens the revision R1 and work on it to make revision R2. In a training Run, you can also select which revision Table to display in that Run, which will allow you to work on editing any revision on a training Run. Please refer this How-to page for more https://docs.3lc.ai/3lc/latest/how-to/basics/run-details.html.
", "votes": null, "replies": [] } ] } ], "raw_markdown_by_id": { "3312526": "How to share same table across teammates?", "3319025": "3LC projects (including Tables and Runs) are designed to be shareable. There are multiple ways to share 3LC projects.\n\n- If your project is located in a common place (e.g., aws s3) that you and your teammates can access, anyone of your team can put the project's URL under \"project-scan-urls\" in the config.yaml file. To learn where to find the config file at https://docs.3lc.ai/3lc/latest/user-guide/file-locations.html \n- You can send the 3LC project to your teammates. Also use the link above to find where your project is. \n- You can also just share/send a data revision Table to your teammates. A data revision Table is located at \"[project name]/datasets/[dataset name]/tables/[table name]\". For this to work, the prior revisions on this dataset has to be the same across the users, because a child revision Table is dependent on its parent revision Table. \n\nFor all these options to share, one thing that is needed to be taken care of is aliases. For example, if all the images are written and stored in absolute paths when creating 3LC Tables, you can imagine the images won't be able to loaded when they open the same Tables from their machine. To learn more about aliases, please refer to this Doc at https://docs.3lc.ai/3lc/latest/user-guide/sharing.html.", "3319047": "One more thing about collaboration: If multiple people work on editing the data and committing revisions, the best practice is to work on it in sequence rather than simultaneously. This is because of the same reason stated above - a child revision is dependent on its parent revision. All the revisions should be in the same lineage tree. For example, 1st person made some edits and committed a revision R1, then the 2nd person opens the revision R1 and work on it to make revision R2. In a training Run, you can also select which revision Table to display in that Run, which will allow you to work on editing any revision on a training Run. Please refer this How-to page for more https://docs.3lc.ai/3lc/latest/how-to/basics/run-details.html." }, "source": "meta" }