Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Extension of ast_contract table

Cesare
Tera Contributor

Hi all, I need to extend ast_contract table.
I know that the role to manage contracts is contract_manager and is requester type.
How does licensing works in this case? It maintains the same logic of the parent table?

1 ACCEPTED SOLUTION

Fabian Kunzke
Mega Sage

Hello,

 

Usually tables maintain the licensing from their parent table, yes. However, please keep in mind that this will also consume a custom table entitlement and needs to be covered by your licensing. Generally speaking license discussions are best picked up with your account manager.


Regards

Fabian

View solution in original post

4 REPLIES 4

Fabian Kunzke
Mega Sage

Hello,

 

Usually tables maintain the licensing from their parent table, yes. However, please keep in mind that this will also consume a custom table entitlement and needs to be covered by your licensing. Generally speaking license discussions are best picked up with your account manager.


Regards

Fabian

Thanks @Fabian Kunzke , yeah for sure!
The custom table is already covered by the licensing.

ChallaR
Giga Guru

Hi @Cesare ,

Yes. Extending ast_contract does not change licensing by itself. Licensing follows the same logic as the parent table.

  • Licensing is role‑based, not table‑based.
  • Users who can create/edit contracts (for example with contract_manager) are considered fulfillers and consume a paid license.
  • End users who only view or reference contracts do not consume a fulfiller license.

So: extending ast_contract is safe from a licensing perspective—only the roles you give to users determine license impact, not the extension.

 

Thanks,

Rithika.ch

Cesare
Tera Contributor

Hi @ChallaR , only one point, contract_manager role is requester and not fullfiller. 🙂