> ## Documentation Index > Fetch the complete documentation index at: https://superofficeas-bugfix-ty-screen-designer-paradox.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # ExternalEvent table > The definition of projects as events in Audience (or other Collaborative apps) ## ExternalEvent Table (233) The definition of projects as events in Audience (or other Collaborative apps) ## Fields | Name | Description | Type | Nullable | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | :------: | | ExternalEvent\_id | Primary key | PK | No | | eventEnabled | Is the event enabled | Bool | No | | eventDate | Dateof the event; publishing/visibility dates are in Publish, and restrictions are in AudienceVisibility | DateTime | No | | parentTable | The thing, that has now become an Event | TableNumber | No | | parentRecord | The thing, that has now become an Event | RecordId | No | | signOn | Is Sign On functionality enabled | Bool | No | | signOnTaskEnable | If not 0, a task should be created when the external user Signs On to an event | Bool | No | | signOnTaskId | If not 0, sign on should cause an Activity of this type to be registered | FK [Task](./task.mdx) | No | | signOnAssocId | If 0, the signOn Activity should go into the persons Our Contact; if not 0, this is the Associate whose diary should get the activity | FK [associate](./associate.mdx) | No | | signOnTextId | If not 0, the given text should be entered into the appointment | FK [text](./text.mdx) | No | | signOnConfTextId | If not 0, the given text should be shown as a confirmation text before accpting Sign On | FK [text](./text.mdx) | No | | signOnTriggersAssign | If 1, the SignOn task should be created as an Assigned task, triggering the invitation dialog | Bool | No | | signOff | Is Sign Off functionality enabled | Bool | No | | signOffTaskEnable | If not 0, a task should be created when the external user Signs Off an event | Bool | No | | signOffTaskId | If not 0, sign off should cause an Activity of this type to be registered | FK [Task](./task.mdx) | No | | signOffAssocId | If 0, the signOn Activity should go into the persons Our Contact; if not 0, this is the Associate whose diary should get the activity | FK [associate](./associate.mdx) | No | | signOffTextId | If not 0, the given text should be shown as a confirmation text before accpting Sign Off | FK [text](./text.mdx) | No | | signOffConfTextId | If not 0, the given text should be shown as a confirmation text before accpting Sign Off | FK [text](./text.mdx) | No | | signOffTriggersAssign | If 1, the SignOff task should be created as an Assigned task, triggering the invitation dialog | Bool | No | | registered | Registered when | UtcDateTime | No | | registered\_associate\_id | Registered by whom | FK [associate](./associate.mdx) | No | | updated | Last updated when | UtcDateTime | No | | updated\_associate\_id | Last updated by whom | FK [associate](./associate.mdx) | No | | updatedCount | Number of updates made to this record | UShort | No | ExternalEvent table relationship diagram ## Indexes | Fields | Types | Description | | ------------ | ----------- | ----------- | | eventEnabled | Bool | Index | | eventDate | DateTime | Index | | parentTable | TableNumber | Index | | parentRecord | RecordId | Index | ## Relationships | Table | Description | | ------------------------ | ------------------------------------------------------------------ | | [associate](./associate) | Employees, resources and other users - except for External persons | | [Task](./task) | Task list table, activity types, like Phone, Meeting | | [text](./text) | Long text fields from all over the system | ## Replication Flags * Replicate changes DOWN from central to satellites and travellers. * Replicate changes UP from satellites and travellers back to central. * Copy to satellite and travel prototypes. ## Security Flags * No access control via user's Role.