Submit ticket based on subscription

Yes this was recently implemented. This is what you want to do.

Create the plan from emerald control panel. Set the count limit to 'yes' and 'count ever access', and set the usage limits, say '1' if you only want the user to be able to use this plan once, or set duration, say '1' month if you want the user to be able to use this plan for a month, or both and the limits can work together.

Now go to cobalt in the backend, add new field and setup the form tab information, then select the emerald tab and locate 'restrict add', select the plan you just created and set the count limit to 'yes'.

Now at the font end, unless the user has a subscription, the field will not be available and it should prompt the user to purchase the field.

You can insert 'default field values' through cobalt field parameters.

If you have multiple fields of this kind, they will all show on the form, however the only fields the user has access to will be available.

In addition to @enocasino's perfect explanation, you have to set submit restriction with Emerald in type parameters.

So let's say you have 3 plans. YOu select there 3 plans. It means only subscribed user will be able to post. Then you limit fields. Field A with plan 1, fields A and B with plan 2.

enocasino If you have multiple fields of this kind, they will all show on the form, however the only fields the user has access to will be available.

This is what I'm trying to avoid.

Let's say we have 2 fields, one for gallery and one for video. Both fields are subscription based. This fields are for submiting let's say "media content type".

Now I have another type, which is support. If user has gallery subscription he can submit question about gallery and if user also has video gallery he can submit question about videos or gallery. But in this case 2 fields will be visible in the form. I don't want to show all fields, I just want to show 1 with "gallery" and "video" options in select.

You can also create a rule that protect add new item URL including cat_id parameter. For example rule for Cobalt view = form and cat_id = 2,12

Sergey You can also create a rule that protect add new item URL including cat_id parameter. For example rule for Cobalt view = form and cat_id = 2,12

THIS! :)