Portal behaviour...

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • just_me
    Member
    • Jul 2019
    • 41

    Portal behaviour...

    I created a basic plus entity called projects. in that one i created an entry for a consulting job for an external consultant.
    Then i created the contact for the consultant and i have a relationship to contacts, where i can select in a single select field, which contact is the one in question.
    Then i created a portal, so the consultant is able to see our meetings and being able to create and work on assigned Tasks.
    Then i created a bunch of meetings, adding my internal users and his contact to that meeting.
    In Portal the portal has access to meetings, tasks, Projects and KB. SInce i do NOT want him to see every entry, i created the role consultant, which gives him access to above mentioned modules and also gave him create right, read right (contact), edit right (contact) and denied the others.

    Now he can see the meetings i added him to, he can click on edit, but he cannot edit. He has to add meeting minutes after each meeting, but he can't.
    Next is, if i set the dashboard to show his activities for the next 30 days, it wouldnt. When i open that window again, the 30 days have been reset to 3 (therefore it doesn't show anything, because the next meeting is in 6 days, not in 3)

    He cannot see the project, although there is a relationship between Projects Module and contacts, and he has only access to projects, where he is asssigned as a contact.

    Might be i am mistaken or barking up the wrong tree, but isn't that the purpose for the portal?

    Any advice?

    Tia
    j_m



  • victor
    Active Community Member
    • Aug 2022
    • 847

    #2
    I unfortunately understood only the following question:

    He cannot see the project, although there is a relationship between Projects Module and contacts, and he has only access to projects, where he is asssigned as a contact.
    If you have created a Portal Role for the Project custom entity with permission to view "contact", then a Portal User with this Portal Role should only see those projects that he is related to.
    For example, you have three records: project1, project2 and project3.
    The Portal User (his Contact) is specified only in project3. So this Portal User will only see project3. And to see project1 and project2, you need to add the Contact of this Portal User to these records.

    Comment

    Working...