DWHPro Insights

Teradata Access Rights: Implicit, Explicit, Inherited, and Automatic

By Roland Wenzlofsky · Published · Updated
Tested on Teradata 20.00.28.81 · metadata query syntax only

Teradata Access Rights: Implicit, Explicit, Inherited, and Automatic

Teradata access can come from ownership, explicit grants, automatic grants and roles. A missing row in one rights view does not prove that a user cannot access an object. Check the actual account, active role, object hierarchy and operation before changing grants.

Lab check: 24 October 2026 · Teradata 20.00.28.81 · BTEQ 20.00.00.11 · BTET. The three zero-row probes below completed successfully under the lab administrator. They validate view/column availability, not another user’s permissions or role inheritance. Download the SQL and observed results.

Read-only checks for the rights dictionary

SELECT UserName, DatabaseName, TableName, AccessRight, GrantAuthority
FROM DBC.AllRightsV WHERE 1=0;
SELECT RoleName, Grantee FROM DBC.RoleMembersV WHERE 1=0;
SELECT RoleName, DatabaseName, TableName, AccessRight
FROM DBC.AllRoleRightsV WHERE 1=0;

Expected and observed result: each query completed with zero rows. WHERE 1=0 intentionally avoids returning account or object details. For an authorized investigation, replace it with predicates for the affected user, role and object; do not interpret this probe as an inventory of grants.

Official AllRoleRightsV reference and dictionary examples. Rights-view access itself depends on privileges.

Types of Teradata Access Rights

Teradata categorizes access privileges into four types:

  1. Implicit: The Teradata privileges of a user or database owning an object (“ownership privilege”)
  2. Explicit: The privileges explicitly granted with the GRANT statement
  3. Inherited: The privileges inherited by being a role member
  4. Automatic: The privileges automatically granted by Teradata

Owners and Creators

Teradata distinguishes between creators and owners of database entities.

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

The creator of an object is the user who executes the DDL statement for its creation. As a result, only a single user can have this role.

The database object’s owners comprise all users and databases positioned higher in the database hierarchy.

The database of a new object is referred to as its immediate owner.

If DBA creates an “Object,” they are the creator, while “System Admin” and “Database 1” are the owners.

perm1

Teradata Access Rights – Implicit Privileges

Ownership can supply implicit authority, but it does not confer every special privilege without restriction. Check the exact operation, privilege and grant authority; procedure creation in particular can require additional rights.

The “System Admin” and “Database 1” databases possess implicit privileges on the “Object”.

Teradata Access Rights – Explicit Privileges

Explicit privileges are managed through the use of GRANT and REVOKE statements.

GRANT assigns object privileges to authorized users, databases or roles as supported by the privilege. Tables, indexes and views are objects on which privileges apply, not general privilege recipients.

GRANT <privileges> ON <object> TO <user> [WITH GRANT OPTION];

To grant explicit privileges, the granting user needs to have the same privileges on this object and grant authority (“WITH GRANT OPTION”)

Explicit grants may be revoked upon fulfillment of the following requirements:

  • We have the permission to grant the permissions, or
  • We are the owner of the object.

Automatic Privileges

Certain privileges are automatically granted when a user creates an object, such as users, databases, tables, views, etc. Automatic privileges are automatically granted by Teradata (“Creator Privilege”). If a table is created, the assigned privileges are DELETE, INSERT, UPDATE, SELECT, etc.

Suppose a user creates a new database or user. In that case, they will receive automatic permissions on the object, and the new object will be granted certain privileges, including delete, insert, update, and select.

Inherited Privileges

Privileges inherited through roles simplify administration by allowing for the assignment of multiple rights to a user through a single role. This eliminates the need to assign individual rights repeatedly to each user. They are therefore available indirectly through an assigned role rather than being granted to a user directly. This approach is preferred for granting permissions.

Why can a user SELECT without a visible direct grant?

Direct grants are only one source of access. Check ownership and the active role, including the relevant role hierarchy. Query the appropriate rights and membership views with authorized access. A missing direct-grant row is not a complete effective-permissions calculation.

Why does the query work in one client but fail in another?

Compare the login identity, current role, default database, fully qualified object name and exact operation. A successful SELECT does not establish INSERT or grant authority. Verify the failure in the affected session before requesting the least additional privilege needed.

Why did REVOKE not remove access?

Access can remain through another grant path, role or ownership. Document all applicable sources rather than repeating REVOKE against the same row. The zero-row tests above do not exercise these authorization paths.

Deciding what to change in your data platform?

Compare optimisation, modernisation and migration against your workload and business requirements.

Explore independent platform assessments

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Follow DWHPro in Google to see our articles more often in Search.

4 thoughts on “Teradata Access Rights: Implicit, Explicit, Inherited, and Automatic”

  1. Hi Roland,
    Good basic information clearly presented. Well done.

    However, I think that your description of ‘inherited’ Access Rights is missing something. I understand why you’ve described Access Rights from Roles as being inherited (I’d never thought of them that way but I see your point), but the term ‘inherited Access Right’ is often used to describe something else.

    An ‘inherited’ Access Right is one that is granted to a user/database specifically during the “CREATE USER/DATABASE” command. Assume the following hierarchy and commands.

    A user name DEV_USERS exists.
    The following command is executed: “GRANT SELECT ON db1 TO ALL DEV_USERS;”
    The following command is now executed: “CREATE USER Fred FROM DEV_USERS;”

    As a result of this (specifically the ‘ALL DEV_USERS’), when ‘fred’ is created, this userid will also be granted the SELECT Access Right on database ‘db1’. this user has inherited the Access Right from an owner.

    Cheers,
    Dave

    Reply

Leave a Comment

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Protected by Security by CleanTalk and CleanTalk Anti-Spam