add workspaces #5651
Comments
|
Other than replicating Trello (which I don't think is an objective of Deck), what are you trying to achieve with the workspace>board levels of permission? |
|
Functionally we are looking to implement this across a multi-branch environment
Workspace>Board>Card setup would look like this
Starting with 22 workspaces (branches) and 10 Boards in each
branchA>Automotive>Task1 etc
design>Card 1
financial> Card 1
branchB>Automotive>Task1 etc
design>Card 1
financial> Card 1
Managers at branchA would have access to all cards in their workspace, Boards would be isolated permissions per pertinent group
Head office automotive would have access to all automotive boards, but not design etc
Regional management has access to Branch A B and C but not D E F
Does that help clarify?
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better™
e: ***@***.******@***.***>
From: Chris Puttick ***@***.***>
Sent: Thursday, March 7, 2024 11:06 AM
To: nextcloud/deck ***@***.***>
Cc: Brendan Plett ***@***.***>; Author ***@***.***>
Subject: Re: [nextcloud/deck] add workspaces (Issue #5651)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
CAUTION: This email originated from outside the organization.
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Other than replicating Trello (which I don't think is an objective of Deck), what are you trying to achieve with the workspace>board levels of permission?
—
Reply to this email directly, view it on GitHub<#5651 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGYUVR4KBHPAHBLPKOGGEI3YXCM6VAVCNFSM6AAAAABELLZQJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGAYTQNJRGU>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
|
I haven't worked that through entirely, but it sounds like "Teams" (aka "Circles") might be the solution or part of it, |
|
I investigated teams/circles, and while it will assist with easier permissions management(similar to groups in AD), it doesn’t address the root of the issue.
Essentially its two layers of permissions required
As well to organize, “folder inside a folder” or a “board inside a workspace”, otherwise some users will see 110 (11Branches*10subjects) boards and have to sort through them
Let me know if you want me to explain further,
I appreciate your responses
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better™
e: ***@***.******@***.***>
From: Chris Puttick ***@***.***>
Sent: Thursday, March 7, 2024 11:26 AM
To: nextcloud/deck ***@***.***>
Cc: Brendan Plett ***@***.***>; Author ***@***.***>
Subject: Re: [nextcloud/deck] add workspaces (Issue #5651)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
CAUTION: This email originated from outside the organization.
Do not click links or open attachments unless you recognize the sender and know the content is safe.
I haven't worked that through entirely, but it sounds like "Teams" (aka "Circles") might be the solution or part of it,
—
Reply to this email directly, view it on GitHub<#5651 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGYUVR5QSAXXJFT6SOP5ODLYXCPKJAVCNFSM6AAAAABELLZQJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGA2TINJSHA>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
|
Good morning,
any chance you can tell me where this is at?
not possible
doesnt fit with the road map
still thinking
thanks
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better™
e: ***@***.******@***.***>
p: 204.326.3481
…________________________________
From: Brendan Plett
Sent: Thursday, March 7, 2024 11:14 AM
To: 'nextcloud/deck' ***@***.***>; nextcloud/deck ***@***.***>
Cc: Author ***@***.***>
Subject: RE: [nextcloud/deck] add workspaces (Issue #5651)
Functionally we are looking to implement this across a multi-branch environment
Workspace>Board>Card setup would look like this
Starting with 22 workspaces (branches) and 10 Boards in each
branchA>Automotive>Task1 etc
design>Card 1
financial> Card 1
branchB>Automotive>Task1 etc
design>Card 1
financial> Card 1
Managers at branchA would have access to all cards in their workspace, Boards would be isolated permissions per pertinent group
Head office automotive would have access to all automotive boards, but not design etc
Regional management has access to Branch A B and C but not D E F
Does that help clarify?
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better™
e: ***@***.******@***.***>
From: Chris Puttick ***@***.***>
Sent: Thursday, March 7, 2024 11:06 AM
To: nextcloud/deck ***@***.***>
Cc: Brendan Plett ***@***.***>; Author ***@***.***>
Subject: Re: [nextcloud/deck] add workspaces (Issue #5651)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
CAUTION: This email originated from outside the organization.
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Other than replicating Trello (which I don't think is an objective of Deck), what are you trying to achieve with the workspace>board levels of permission?
—
Reply to this email directly, view it on GitHub<#5651 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGYUVR4KBHPAHBLPKOGGEI3YXCM6VAVCNFSM6AAAAABELLZQJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGAYTQNJRGU>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
|
Good afternoon,
Can this conversation be revived? I am just wondering where we stand
thanks
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better(tm)
e: ***@***.******@***.***>
p: 204.326.3481
From: Brendan Plett ***@***.***>
Sent: Tuesday, March 12, 2024 10:54 AM
To: 'nextcloud/deck' ***@***.***>; nextcloud/deck ***@***.***>
Cc: Author ***@***.***>
Subject: Re: [nextcloud/deck] add workspaces (Issue #5651)
Good morning,
any chance you can tell me where this is at?
not possible
doesnt fit with the road map
still thinking
thanks
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better(tm)
e: ***@***.******@***.***>
p: 204.326.3481
…________________________________
From: Brendan Plett
Sent: Thursday, March 7, 2024 11:14 AM
To: 'nextcloud/deck' ***@***.******@***.***>>; nextcloud/deck ***@***.******@***.***>>
Cc: Author ***@***.******@***.***>>
Subject: RE: [nextcloud/deck] add workspaces (Issue #5651)
Functionally we are looking to implement this across a multi-branch environment
Workspace>Board>Card setup would look like this
Starting with 22 workspaces (branches) and 10 Boards in each
branchA>Automotive>Task1 etc
design>Card 1
financial> Card 1
branchB>Automotive>Task1 etc
design>Card 1
financial> Card 1
Managers at branchA would have access to all cards in their workspace, Boards would be isolated permissions per pertinent group
Head office automotive would have access to all automotive boards, but not design etc
Regional management has access to Branch A B and C but not D E F
Does that help clarify?
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better(tm)
e: ***@***.******@***.***>
From: Chris Puttick ***@***.******@***.***>>
Sent: Thursday, March 7, 2024 11:06 AM
To: nextcloud/deck ***@***.******@***.***>>
Cc: Brendan Plett ***@***.******@***.***>>; Author ***@***.******@***.***>>
Subject: Re: [nextcloud/deck] add workspaces (Issue #5651)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
CAUTION: This email originated from outside the organization.
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Other than replicating Trello (which I don't think is an objective of Deck), what are you trying to achieve with the workspace>board levels of permission?
-
Reply to this email directly, view it on GitHub<#5651 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGYUVR4KBHPAHBLPKOGGEI3YXCM6VAVCNFSM6AAAAABELLZQJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGAYTQNJRGU>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
|
Good morning,
Is it possible in the future to have board management as discussed earlier?
Even grouping for personal management of 100 boards, to be able to create folders for them to be placed in?
thanks
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better(tm)
e: ***@***.******@***.***>
p: 204.326.3481
From: Brendan Plett
Sent: Wednesday, March 20, 2024 1:12 PM
To: 'nextcloud/deck' ***@***.***>; nextcloud/deck ***@***.***>
Cc: Author ***@***.***>
Subject: RE: [nextcloud/deck] add workspaces (Issue #5651)
Good afternoon,
Can this conversation be revived? I am just wondering where we stand
thanks
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better(tm)
e: ***@***.******@***.***>
p: 204.326.3481
From: Brendan Plett ***@***.******@***.***>>
Sent: Tuesday, March 12, 2024 10:54 AM
To: 'nextcloud/deck' ***@***.******@***.***>>; nextcloud/deck ***@***.******@***.***>>
Cc: Author ***@***.******@***.***>>
Subject: Re: [nextcloud/deck] add workspaces (Issue #5651)
Good morning,
any chance you can tell me where this is at?
not possible
doesnt fit with the road map
still thinking
thanks
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better(tm)
e: ***@***.******@***.***>
p: 204.326.3481
…________________________________
From: Brendan Plett
Sent: Thursday, March 7, 2024 11:14 AM
To: 'nextcloud/deck' ***@***.******@***.***>>; nextcloud/deck ***@***.******@***.***>>
Cc: Author ***@***.******@***.***>>
Subject: RE: [nextcloud/deck] add workspaces (Issue #5651)
Functionally we are looking to implement this across a multi-branch environment
Workspace>Board>Card setup would look like this
Starting with 22 workspaces (branches) and 10 Boards in each
branchA>Automotive>Task1 etc
design>Card 1
financial> Card 1
branchB>Automotive>Task1 etc
design>Card 1
financial> Card 1
Managers at branchA would have access to all cards in their workspace, Boards would be isolated permissions per pertinent group
Head office automotive would have access to all automotive boards, but not design etc
Regional management has access to Branch A B and C but not D E F
Does that help clarify?
Brendan Plett
Systems Manager
McMunn & Yates Building Supplies | Make it Better(tm)
e: ***@***.******@***.***>
From: Chris Puttick ***@***.******@***.***>>
Sent: Thursday, March 7, 2024 11:06 AM
To: nextcloud/deck ***@***.******@***.***>>
Cc: Brendan Plett ***@***.******@***.***>>; Author ***@***.******@***.***>>
Subject: Re: [nextcloud/deck] add workspaces (Issue #5651)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
CAUTION: This email originated from outside the organization.
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Other than replicating Trello (which I don't think is an objective of Deck), what are you trying to achieve with the workspace>board levels of permission?
-
Reply to this email directly, view it on GitHub<#5651 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGYUVR4KBHPAHBLPKOGGEI3YXCM6VAVCNFSM6AAAAABELLZQJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGAYTQNJRGU>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
looking to add another level of permissions for deck
currently it is Board>Card, looking for Workspace>Board>Card
this would replicate Trello.
How to use GitHub
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: