<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>User &amp; Access on Learn Oracle OTM</title><link>https://www.oracle-otm.com/posts/user-access/</link><description>Recent content in User &amp; Access on Learn Oracle OTM</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 08 Jan 2018 22:53:00 +0000</lastBuildDate><atom:link href="https://www.oracle-otm.com/posts/user-access/index.xml" rel="self" type="application/rss+xml"/><item><title>User Roles - VPD and Access Control Lists</title><link>https://www.oracle-otm.com/posts/user-roles-vpd-and-access-control-lists/</link><pubDate>Thu, 01 Dec 2016 21:30:00 +0000</pubDate><guid>https://www.oracle-otm.com/posts/user-roles-vpd-and-access-control-lists/</guid><description>&lt;div class="note-box"&gt;In OTM, access control for a user is defined through a &lt;strong&gt;User Role&lt;/strong&gt; — a container that groups two distinct types of restrictions that must be configured together:
&lt;p&gt;&lt;strong&gt;VPD (Virtual Private Database)&lt;/strong&gt; controls &lt;em&gt;data-level&lt;/em&gt; visibility. It operates at the database row level, silently filtering query results so that a user only ever sees records they are permitted to access — for example, a planner restricted to their own region&amp;rsquo;s shipments, or an approver who can only see invoices within their approval threshold. VPD rules are invisible to the user: the application does not show a filtered view, it simply never returns rows they are not permitted to see.&lt;/p&gt;</description></item><item><title>User Menu and Manage User Access</title><link>https://www.oracle-otm.com/posts/user-menu-and-manage-user-access/</link><pubDate>Wed, 05 Apr 2017 20:10:00 +0000</pubDate><guid>https://www.oracle-otm.com/posts/user-menu-and-manage-user-access/</guid><description>&lt;p&gt;Once a user logs in to the application, they will have access to OTM functions based on the role associated to their user record. You can further restrict the menu at role level or user level by creating a custom menu and associating it to the user or role.&lt;/p&gt;
&lt;p&gt;Note that while creating a user, the following values are mandatory:&lt;/p&gt;
&lt;div class="step-box"&gt;Configuration and Administration &gt; User Management &gt; User Manager&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;div class="field-box"&gt;&lt;strong&gt;User ID:&lt;/strong&gt; Unique identifier for the user&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div class="field-box"&gt;&lt;strong&gt;User Name:&lt;/strong&gt; Can be used to avoid entering the domain name at login&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div class="field-box"&gt;&lt;strong&gt;Password:&lt;/strong&gt; Initial password for the user&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div class="field-box"&gt;&lt;strong&gt;User Role ID:&lt;/strong&gt; Default role for that user after initial login&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can restrict the menu so that a user sees only specific screens — for example, only the Purchase Order (Order Base) screen. First create a custom menu with that single screen set link, then associate the menu to the user or role.&lt;/p&gt;</description></item><item><title>Service Provider User Login creation</title><link>https://www.oracle-otm.com/posts/service-provider-user-login-creation/</link><pubDate>Mon, 08 Jan 2018 22:53:00 +0000</pubDate><guid>https://www.oracle-otm.com/posts/service-provider-user-login-creation/</guid><description>&lt;p&gt;In OTM, service providers such as carriers can be given their own login credentials to accept tenders and view shipment data. This article explains how to configure service provider user logins and the Manage Association setup that restricts each user to their specific carrier&amp;rsquo;s data.&lt;/p&gt;
&lt;p&gt;First, create a service provider (for example, ABCD) in the required domain (for example, DOMN).&lt;/p&gt;
&lt;p&gt;You can then log in as SERVPROV.ADMIN with the default password of &amp;lsquo;CHANGEME&amp;rsquo;, or check with your system administrator if this password has been updated.&lt;/p&gt;</description></item></channel></rss>