Reltio Connect

 View Only
  • 1.  Business and IT Roles

    Posted 07-28-2021 17:58

    We have just signed Reltio contract 10 days back.  Reltio tenants were available in 3-4 days.   We are still figuring our connectivity between us and Reltio, SSO, whitelisting, source system connectivity etc.  While we are at very early stage, I hoping that experience Reltio customer have figured out the kind of business and IT roles that make sense and work in Reltio.  I know it depends on each business but I am sure for most business, the roles can be pretty much common.  I have search in the community but I did not find anything on this. I have also quickly looked at securitymanagement and it have great information but I don't think it helps much on what kind roles we as a customer should be creating.   I would appreciate if someone can share what they have done it in their organization.

    Here is what I think we will need (I am assuming each person can have multiple roles if they need):

    By each Business domain

    • Data Stewards
    • Data Stewards Manager (SLA escalation, special approval) 
    • Reader/Viewer
    • PII (if applicable)


    IT Roles

    • Admin
    • Configurator
    Any help would be appreciated!!

    Nishit Ajwaliya
    Enterprise Information Architect
    National Grid

  • 2.  RE: Business and IT Roles

    Reltio Employee
    Posted 07-29-2021 14:15
    @David Starnes, @Walt Feldman, @Angela Wawrzaszek, I know that you have a ton of expertise. What do you think? ​​​

  • 3.  RE: Business and IT Roles

    Reltio Employee
    Posted 07-29-2021 17:06

       This is a great question and something I think a lot of customer struggle with at the beginning.  I think you are on the right path on segmenting the roles into 2 paths.  I would look at it the same way.  Let me try to cover the IT roles first.

    IT Roles:


    You are going to have a single customer admin setup when you get your tenants.  This can be changed in the future, but this person is the super user for your platform.  I would just make this person your top level administrator for Reltio.  They should be technical and definitely know enough to be dangerous.


    During implementation (and even ongoing if you are follow a continuous improvement agile methodology), you will probably have some developers who are doing things like adding / editing the data model, adjusting match rules etc.  Typically, I see these people get almost the same access as an admin, they may just only have this for dev and test tenants.  It is important these resources can see data and use the business user capabilities as well so that they can effectively test and verify the changes that they are making.

    We don't tend to see significant granularity beyond that for the IT side.  Some customers do try to limit access to data, but it creates significant challenges in deploying your tenant config properly, and I would suggest that development teams need to see the data in order to do their jobs well.

    Business Roles:

    Most of our customers break down roles on the business side to one of the following.  There may be multiple flavors of Data Steward if say someone can only see US data, or only see EU data, but the core of the role is the same, they just apply it to only a certain geography.

    Data Steward :

    Someone who can edit or suggest edits to data in Reltio.  These team members are typically resolving potential matches and applying changes in the platform.  They are typically UI only users.  For complex multi geography tenants, there may be different flavors of data stewards primarily to limit access to data based on geography or entity type.

    Data Steward Elevated (Manager / level 2)

    Most orgs that I have worked with do not have this role, but a sizable amount do.  These are for when your level 1 stewards are only suggesting changes.  These resources actually make the final call.  They have typically the same permissions as a Data Steward except they can edit things vs just suggesting things.

    Read Only:

    Almost everyone sets up a read only role.  This is for anyone who wants to search the data and view things inside of the UI.  These read only roles can be broken down to limit access as well if desired.

    In a final note, I would suggest that you start with these basic roles and create specific flavors of them as needed.  Sometimes customers start with trying to create as many possible configurations of roles that they can think of and end up with an unmanageably mess of roles as they onboard more and more users.  I am hoping some of our other customers and partners will also add their thoughts as well!

    Mike Frasca

  • 4.  RE: Business and IT Roles

    Founding Member
    Posted 07-29-2021 21:56
    My experience may be somewhat unique, but I am happy to share it. This is how we set up the role structure:

    1. Admin - very limited, 1-2 people in IT org
    2. Developer - given to many developers, QA testers, MarTech folks and so on. Only access non-prod tenants, which looks and function like prod but contains no "real" PII. 
    3. Steward - the very same 1-2 people as admin. While this may seem odd to some, most stewarding is "self service" via the mobile app or website, and there is no merging due to use of surrogate crosswalks. Most "stewarding" is actually data cleanups from various issues introduced from the app or website.
    4. Read-only - this is the bulk of the production access, mostly given to the guest care team (folks who respond to support calls & emails) and select folks in Digital Marketing/MarTech. If any of the read only users spot a data quality issue that cannot be resolved "self service", they escalate to the admin/steward.

  • 5.  RE: Business and IT Roles

    Founding Member
    Posted 07-30-2021 11:27
    Our Organization is very small for the MDM Landscape.  We have our Roles set up as the following:
    1. Admin - (2),  Myself and 1 Data Steward whom is more of a leader role.
    2. Developer - 1      has access to all Tenants and responsible for all configuration changes and Jar applications for PUblishing Data.      There is also 1 (limited time as needed) for all ETL devleopment for loading Data and processing the Published Data for the Data Warehouse. 
    3.  Data Stewards (3 for US),    1 for each of the 10 Outside US countries using the MDM data.    They spend the bulk of the time reviewing Potential Matches across the 9 systems being loaded to Reltio.     I will need to go back and find out more on the 'Surrogate Key' Walt mentioned that allows them to not have to review matches!!   We have been stewarding for 4 years and are no where close to being done (400K to go!)  We also have around 4K in new customers added a month.
    4.  Read-Only   - bulk of access for any Business user wanting access,  many have,  most log in very rarely. 

    Hope that helps!