sib_user.inviteuser: Sendinblue Package for User operations that could not be mapped to a table. |
`Feature` - A Feature represents a specific functionality like Emailcampaign, Deals, Calls, Automations, etc. on Brevo. While inviting a user,determine which feature you want to manage access to. You must specify thefeature accurately to avoid errors. `Permission` - A Permission defines thelevel of access or control a user has over a specific feature. Whileinviting user, decide on the permission level required for the selectedfeature. Make sure the chosen permission is related to the selected feature.Features and their respective permissions are as below: - `email_campaigns`:- "create_edit_delete"- "send_schedule_suspend"- `sms_campaigns`:- "create_edit_delete"- "send_schedule_suspend"- `contacts`:- "view"- "create_edit_delete"- "import"- "export"- "list_and_attributes"- "forms"- `templates`:- "create_edit_delete"- "activate_deactivate"- `workflows`:- "create_edit_delete"- "activate_deactivate_pause"- "settings"- `landing_pages`:- "all"- `transactional_emails`:- "settings"- "logs"- `smtp_api`:- "smtp"- "api_keys"- "authorized_ips"- `user_management`:- "all"- `sales_platform`:- "create_edit_deals"- "delete_deals"- "manage_others_deals_tasks"- "reports"- "settings"- `phone`:- "all"- `conversations`:- "access"- "assign"- "configure"- `senders_domains_dedicated_ips`:- "senders_management"- "domains_management"- "dedicated_ips_management"- `push_notifications`:- "view"- "create_edit_delete"- "send"- "settings"- `companies`:- "manage_owned_companies"- "manage_other_companies"- "settings"**Note**: - If `all_features_access: false` then only privileges arerequired otherwise if `true` then it's assumed that all permissions will bethere for the invited user. - The availability of feature and its permissiondepends on your current plan. Please select the features and permissionsaccordingly.
Parameters of Procedure
The following parameters can be used to control the behaviour of the procedure sib_user.inviteuser. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.
Value specification by position is done by listing all values from the first to the last needed value. For example: a `begin package.procedure(value1, value2, value3); end` on a procedure with four parameters will use the default value for the fourth parameter and the specified values for the first three.
Value specification by name is done by listing all values that require a value. For example with `begin package.procedure(name1 => value1, name3 => value3); end` on the same procedure will use the default values for the second and fourth parameters and the specified values for the first and third.
Name |
Data Type |
Required |
Default Value |
Documentation |
|---|---|---|---|---|
all_features_access |
boolean |
☑ |
|
All access to the features (Values: true, false) |
string |
☑ |
|
Email address for the organization |