This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Role based Access to application - from Lotus notes to Sharepoint Migration

Question-How to map Lotus Notes Roles to SharePoint?

Question-How to provide Role based access to SharePoint application?

Description- We have Lotus notes application which has user permissions as well as roles in it. We are migrating to SharePoint 2016 on-prem and i found we have permissions functionality in it but how to implement Roles along with permissions in SharePoint.

Can someone help us asap.

thanks in advance.Let me know if you need any more details.

anji 

Parents
  • Notes Roles can be migrated to SharePoint Groups using Migrator for Notes to SharePoint using the permission migration options (and the advanced-tab).

    There is no generic answer how to take over Notes Roles functionality alas - that depends a lot on how they were used.
    It can be as easy as using the migrated SharePoint role to assign permissions (giving the "Teachers" Group migrated from the "Teachers" Role access to the Answers-List on a training site). What we see pretty often (also with permissions migration in general) that customers split up data that used to be in one entity (e.g. in one item with several fields, or one list) into several entities (e.g. several lists) to better be able to assign permissions, because SharePoint is not very good at assigning permissions on field level, or managing permissions on single items.

    Hope this helps a little.

Reply
  • Notes Roles can be migrated to SharePoint Groups using Migrator for Notes to SharePoint using the permission migration options (and the advanced-tab).

    There is no generic answer how to take over Notes Roles functionality alas - that depends a lot on how they were used.
    It can be as easy as using the migrated SharePoint role to assign permissions (giving the "Teachers" Group migrated from the "Teachers" Role access to the Answers-List on a training site). What we see pretty often (also with permissions migration in general) that customers split up data that used to be in one entity (e.g. in one item with several fields, or one list) into several entities (e.g. several lists) to better be able to assign permissions, because SharePoint is not very good at assigning permissions on field level, or managing permissions on single items.

    Hope this helps a little.

Children
No Data