[Résolu] Restrict Access To Specific Team Members Only
This support ticket is created Il y a 7 années et 1 mois. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
Hello Access Support Specialist... Would value your assistance.
THE OVERALL GOAL
I have two Custom Access Roles, Manager and Team Member. I need the ability for a Manager to assign Various team members to Projects and all from the front end. So for example if I have 3 projects and I want team member A to be assigned to project 2 and team member B to be assigned to project 1 and 3 they should not be able to access each others projects even if they know the direct url path.
QUESTIONS
1. I see that I can create a view to display projects based on the logged in team member but I presume this does not restrict access to other team members as this Custom Access Role grants read access. So how do I actually lock the project down based on the user?
2. Would it be possible to assign more then one team member to a project, e.g. team member B could also access project 2 if they were assigned by the manager to do so?
3. What role capabilities are necessary so a manager can have access to all projects but restrict them from any WordPress backend functionality.
Hello. Thank you for contacting the Toolset support.
As per our support policy, we will support one question per ticket and this will help other users searching on the forum.
QUESTIONS
1. I see that I can create a view to display projects based on the logged in team member but I presume this does not restrict access to other team members as this Custom Access Role grants read access. So how do I actually lock the project down based on the user?
==> Regarding above question, what if you use shortcode [toolset_access] to restrict the content.
For example:
[toolset_access role="Subscriber,Administrator,Customer" operator="allow"]
your content - will be shown to above roles
[/toolset_access]
[toolset_access role="Customer" operator="deny"]
your content - will be not be shown to above roles
[/toolset_access]
Apologies Minesh... I posted in the manner I did for the benefit of the Toolset Support Staff. As the three inquiries have a bearing on each other, to separate them would cause the overall gist of the inquiry to be less understandable. I will do as you have asked and separate out and repeat all necessary info.
In regards to your above response, not sure you are taking into consideration the gist of the overall question as it does not appear to address the overall need. I am aware of this short code but the documentation seems to imply it is for text and further the goal is to restrict entire pages to specific team members who have the proper user role not restrict based on user role only.
You should create post group but again its limited to read access but I see that you also want ti allow edit rights to few users thats not possible with Access at the moment.
Hello Minesh... I appreciate the link to the documentation but I have spent quite a bit of time with it prior to starting this thread. I have tried to break this out into several fragmented threads but the overall gist gets lost. In the future I will take a different approach to how I ask this sort of question.
I am going to readdress the overall project management need once again in an effort to make things clearer. perhaps this matter should be forwarded to a senior level support person who can address the overall inquiry.
OVERVIEW - PROJECT MANAGER
Project manager (WordPress user role set as Manager) logs in to a front end project management dashboard page that will provide access to all projects as well as the ability to add and delete projects. Within each project the manager has full edit capabilities as well as the ability to assign team members to each project. Note that team members are already set up as WordPress users with the role Team Member, this is done by the admin.
The manager will also have access to a front end page that will display a view of all files uploaded by team members. This page will have the ability to search/sort via views. Note, files will be set up as their own unique post type with an intermediate post type as per current Toolset many-to-many relationship method.
While there will be more custom fields and overall relational functionality to the project management system, I have provided the files scenario as it is important to understanding the need for uploaded files to be secured and identified as belonging to the team member that uploaded them.
OVERVIEW - TEAM MEMBER
Team member (WordPress user role Team Member) logs into the project management dashboard which only displays the projects they have been assigned. From this page the team members can access their projects. Within each project the team member can edit content as well as upload and download files. Note this team members page and it's content is not accessible to other team members with the WordPress role Team Member, even if they know the direct URL path to the page or its content.
QUESTION
I don't see how to assign specific team members with the same user role to project pages and restrict access to the pages and their content based on that specific team member. How do I do this using Toolset Access?
Well, we can lock editing for entire CPT in Access but there is no way to allow editing for the specific user and for the individual post(project).
Unfortunately, there is no native feature that and you can't achieve it with Toolset Access.
Partially It can be achieved with custom coding, yes, custom programming but again, custom programming is out of the scope of our support policy and no support provided for same. If you want custom programming with your project, please feel free to contact our certified partners.
=> https://toolset.com/consultant/
Still - I can show you a way using how you can approach using custom programming but again, you need to check if this fits as per your need.
1. For each project add custom field which is used to hold users ID (members) that can edit that project.
2. ON project list page for members add a filter that will filter received projects and check if Project:custom field:contain user ID and same while editing project check with custom field is user ID is allowed to edit the project.
Hello Minesh... Appreciate the assistance but I don't believe I am understanding your approach.
Adding the custom field is pretty straight forward but I am not seeing how this will allow the manager to assign Team Members to projects or how this controls access to pages based on the Team Member that was assigned to the project?
Adding the custom field is pretty straight forward but I am not seeing how this will allow the manager to assign Team Members to projects
=> For this as I said you need custom programming and that is eventually out of the scope of our support policy. That how you can assign value of team member ids to custom field.
how this controls access to pages based on the Team Member that was assigned to the project?
=> Once you are able to assign team members to projects, you can use again custom shortcode to check if the team member ID is available with your custom field.
All above approach needs custom programming, If you want custom programming with your project, please feel free to contact our certified partners.
=> https://toolset.com/consultant/
Really disappointing... I can easily use another solution, was just trying to embrace a total Toolset approach for building out my Project Management System.
I have read this thread carefully and raised your requirements to higher levels in the team.
Unfortunately, I got a response from the Toolset development team leader that you requirements couldn't be achieved natively using Access.
I see that Minesh provided a good solution that will help you to implement your requirements.
The thing is that we don't know the status of our project and we don't have access to your website.
From my point of view, I see that we can go through your requirements one by one and see which Toolset plugin we can use to Achieve each of your functionality then build the needed pages, views, forms, etc.
If you agree, we will build a test site for you with your requirements implemented there so that you can see the configurations there and also the custom code.
Thanks for your patience and I will be happy if I heard from you soon.
Hello Mohammed... Thank you for reaching out to me. I am currently in the R&D Phase with my companies project management site. All test sites are quite fragmented and only represent various feature testing and such, so they would be of no use.
I stumbled upon Toolset back last November and quite blown away at the potential for using it as a powerful tool to build online solutions for my business. If you are willing to provide this level of support via a Toolset Test site I will fully participate with you on this.
I look forward to your response and moving things forward in a thoughtful and productive manner.
We tried to prepare part of the solution for you so that you can see that how you can apply permission per post based using team member role.
I wanted to share all information - if you share your email ID I'll send you email or if you want we can schedule a video call. If you prefer to have video call, please let us know your preferable time.
=> https://toolset.com/toolset-support-policy/ask-support-video-call/
